{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:e99052ef-87cc-5dd2-84bc-60fc9d937f68", "version": 1, "metadata": { "tools": [ { "name": "tuxcare-vex-generator", "version": "1.0.0" } ] }, "components": [ { "bom-ref": "pkg:maven/org.apache.logging.log4j/log4j-jakarta-smtp@2.22.1-tuxcare.3", "type": "library", "group": "org.apache.logging.log4j", "name": "log4j-jakarta-smtp", "version": "2.22.1-tuxcare.3", "purl": "pkg:maven/org.apache.logging.log4j/log4j-jakarta-smtp@2.22.1-tuxcare.3" } ], "vulnerabilities": [ { "bom-ref": "urn:uuid:8bc4a99a-6446-5dab-909b-625e09fd7cca", "id": "CVE-2014-8180", "analysis": { "state": "false_positive", "detail": "Vulnerability CVE-2014-8180 is a false positive for org.apache.logging.log4j:log4j-jakarta-smtp 2.22.1-tuxcare.3." }, "affects": [ { "ref": "pkg:maven/org.apache.logging.log4j/log4j-jakarta-smtp@2.22.1-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:e9141bc6-b038-50d5-bfae-8dada94e67e4", "id": "CVE-2016-6494", "analysis": { "state": "false_positive", "detail": "Vulnerability CVE-2016-6494 is a false positive for org.apache.logging.log4j:log4j-jakarta-smtp 2.22.1-tuxcare.3." }, "affects": [ { "ref": "pkg:maven/org.apache.logging.log4j/log4j-jakarta-smtp@2.22.1-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:2fdac458-49b5-54d2-be22-b64597c5d607", "id": "CVE-2021-32036", "analysis": { "state": "false_positive", "detail": "Vulnerability CVE-2021-32036 is a false positive for org.apache.logging.log4j:log4j-jakarta-smtp 2.22.1-tuxcare.3." }, "affects": [ { "ref": "pkg:maven/org.apache.logging.log4j/log4j-jakarta-smtp@2.22.1-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:10986529-6beb-5037-ae72-f185c00b23bc", "id": "CVE-2021-38295", "analysis": { "state": "false_positive", "detail": "Vulnerability CVE-2021-38295 is a false positive for org.apache.logging.log4j:log4j-jakarta-smtp 2.22.1-tuxcare.3." }, "affects": [ { "ref": "pkg:maven/org.apache.logging.log4j/log4j-jakarta-smtp@2.22.1-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:285be34e-b9a6-5bd4-9384-71f0a236099c", "id": "CVE-2022-24706", "analysis": { "state": "false_positive", "detail": "Vulnerability CVE-2022-24706 is a false positive for org.apache.logging.log4j:log4j-jakarta-smtp 2.22.1-tuxcare.3." }, "affects": [ { "ref": "pkg:maven/org.apache.logging.log4j/log4j-jakarta-smtp@2.22.1-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:e11b7f8b-305f-53b6-b1f8-6ce1b4090e24", "id": "CVE-2023-26268", "analysis": { "state": "false_positive", "detail": "Vulnerability CVE-2023-26268 is a false positive for org.apache.logging.log4j:log4j-jakarta-smtp 2.22.1-tuxcare.3." }, "affects": [ { "ref": "pkg:maven/org.apache.logging.log4j/log4j-jakarta-smtp@2.22.1-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:19884563-180c-593a-813c-ed24606e134c", "id": "CVE-2023-45725", "analysis": { "state": "false_positive", "detail": "Vulnerability CVE-2023-45725 is a false positive for org.apache.logging.log4j:log4j-jakarta-smtp 2.22.1-tuxcare.3." }, "affects": [ { "ref": "pkg:maven/org.apache.logging.log4j/log4j-jakarta-smtp@2.22.1-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:7ab61108-7c0a-5d04-9e24-57693b645a23", "id": "CVE-2025-68161", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-68161 is fixed in version 2.22.1-tuxcare.3 of org.apache.logging.log4j:log4j-jakarta-smtp." }, "affects": [ { "ref": "pkg:maven/org.apache.logging.log4j/log4j-jakarta-smtp@2.22.1-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:b921c5e0-ed31-57a4-902f-f742a243e300", "id": "CVE-2026-34477", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-34477 affects version 2.22.1-tuxcare.3 of org.apache.logging.log4j:log4j-jakarta-smtp." }, "affects": [ { "ref": "pkg:maven/org.apache.logging.log4j/log4j-jakarta-smtp@2.22.1-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:f1e264fa-00d7-56ae-a578-aa58851ab8a2", "id": "CVE-2026-34478", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-34478 does not affect version 2.22.1-tuxcare.3 of org.apache.logging.log4j:log4j-jakarta-smtp. Version not vulnerable (per prereq analysis); terminalized." }, "affects": [ { "ref": "pkg:maven/org.apache.logging.log4j/log4j-jakarta-smtp@2.22.1-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:35d12193-7de3-5850-9762-18e1ec18c14d", "id": "CVE-2026-34479", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-34479 is fixed in version 2.22.1-tuxcare.3 of org.apache.logging.log4j:log4j-jakarta-smtp." }, "affects": [ { "ref": "pkg:maven/org.apache.logging.log4j/log4j-jakarta-smtp@2.22.1-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:b85c5fa3-50a9-542f-b820-c6ba1eb28377", "id": "CVE-2026-34480", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-34480 does not affect version 2.22.1-tuxcare.3 of org.apache.logging.log4j:log4j-jakarta-smtp. Version 2.22.1 is not vulnerable. Summary: The target repository version 2.22.1-tuxcare.1 is NOT VULNERABLE to CVE-2026-34480. While the XmlLayout feature exists, the sanitization fix that addresses the vulnerability has been backported and is fully implemented in the current codebase. [terminalized not_affected from patch_application_manual/not_vulnerable]" }, "affects": [ { "ref": "pkg:maven/org.apache.logging.log4j/log4j-jakarta-smtp@2.22.1-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:fcdca5fb-605b-52b2-9e7d-c1a439be266e", "id": "CVE-2026-34481", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-34481 is fixed in version 2.22.1-tuxcare.3 of org.apache.logging.log4j:log4j-jakarta-smtp." }, "affects": [ { "ref": "pkg:maven/org.apache.logging.log4j/log4j-jakarta-smtp@2.22.1-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:a2d62c62-9efc-5b17-9081-40df5c8a473a", "id": "CVE-2026-49844", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-49844 is fixed in version 2.22.1-tuxcare.3 of org.apache.logging.log4j:log4j-jakarta-smtp." }, "affects": [ { "ref": "pkg:maven/org.apache.logging.log4j/log4j-jakarta-smtp@2.22.1-tuxcare.3" } ] } ], "dependencies": [ { "ref": "pkg:maven/org.apache.logging.log4j/log4j-jakarta-smtp@2.22.1-tuxcare.3" } ] }