{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:b43ac596-2062-5b0d-a15d-9166c21a30e2", "version": 1, "metadata": { "tools": [ { "name": "tuxcare-vex-generator", "version": "1.0.0" } ] }, "components": [ { "bom-ref": "pkg:maven/org.apache.logging.log4j/log4j-flume-ng@2.22.1-tuxcare.3", "type": "library", "group": "org.apache.logging.log4j", "name": "log4j-flume-ng", "version": "2.22.1-tuxcare.3", "purl": "pkg:maven/org.apache.logging.log4j/log4j-flume-ng@2.22.1-tuxcare.3" } ], "vulnerabilities": [ { "bom-ref": "urn:uuid:436d1c98-bce1-5211-9c15-0570b3db8ac6", "id": "CVE-2014-8180", "analysis": { "state": "false_positive", "detail": "Vulnerability CVE-2014-8180 is a false positive for org.apache.logging.log4j:log4j-flume-ng 2.22.1-tuxcare.3." }, "affects": [ { "ref": "pkg:maven/org.apache.logging.log4j/log4j-flume-ng@2.22.1-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:8daf5fa1-826d-56cc-acbe-6239d3cc1467", "id": "CVE-2016-6494", "analysis": { "state": "false_positive", "detail": "Vulnerability CVE-2016-6494 is a false positive for org.apache.logging.log4j:log4j-flume-ng 2.22.1-tuxcare.3." }, "affects": [ { "ref": "pkg:maven/org.apache.logging.log4j/log4j-flume-ng@2.22.1-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:ec617175-40e0-50d3-ab2d-731e3a12015a", "id": "CVE-2021-32036", "analysis": { "state": "false_positive", "detail": "Vulnerability CVE-2021-32036 is a false positive for org.apache.logging.log4j:log4j-flume-ng 2.22.1-tuxcare.3." }, "affects": [ { "ref": "pkg:maven/org.apache.logging.log4j/log4j-flume-ng@2.22.1-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:034a5dcd-d562-53ec-913e-b3778f0e7692", "id": "CVE-2021-38295", "analysis": { "state": "false_positive", "detail": "Vulnerability CVE-2021-38295 is a false positive for org.apache.logging.log4j:log4j-flume-ng 2.22.1-tuxcare.3." }, "affects": [ { "ref": "pkg:maven/org.apache.logging.log4j/log4j-flume-ng@2.22.1-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:385913b1-c698-5593-93f9-9e85385c189d", "id": "CVE-2022-24706", "analysis": { "state": "false_positive", "detail": "Vulnerability CVE-2022-24706 is a false positive for org.apache.logging.log4j:log4j-flume-ng 2.22.1-tuxcare.3." }, "affects": [ { "ref": "pkg:maven/org.apache.logging.log4j/log4j-flume-ng@2.22.1-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:85683d40-0077-5022-b86b-d02d6738cf86", "id": "CVE-2023-26268", "analysis": { "state": "false_positive", "detail": "Vulnerability CVE-2023-26268 is a false positive for org.apache.logging.log4j:log4j-flume-ng 2.22.1-tuxcare.3." }, "affects": [ { "ref": "pkg:maven/org.apache.logging.log4j/log4j-flume-ng@2.22.1-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:92e8b2c7-e8d6-5320-bfcc-47c69e485a74", "id": "CVE-2023-45725", "analysis": { "state": "false_positive", "detail": "Vulnerability CVE-2023-45725 is a false positive for org.apache.logging.log4j:log4j-flume-ng 2.22.1-tuxcare.3." }, "affects": [ { "ref": "pkg:maven/org.apache.logging.log4j/log4j-flume-ng@2.22.1-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:03b52c39-0e63-55d8-9c5c-aa63a3d4d8e2", "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-flume-ng." }, "affects": [ { "ref": "pkg:maven/org.apache.logging.log4j/log4j-flume-ng@2.22.1-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:c26be0be-fde7-5355-9f8d-9a8a79786a2d", "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-flume-ng." }, "affects": [ { "ref": "pkg:maven/org.apache.logging.log4j/log4j-flume-ng@2.22.1-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:d773e231-f572-5ff9-a968-043ac00ada7e", "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-flume-ng. Version not vulnerable (per prereq analysis); terminalized." }, "affects": [ { "ref": "pkg:maven/org.apache.logging.log4j/log4j-flume-ng@2.22.1-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:946d1cad-b29e-5caf-bd03-a3b9fd7cc480", "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-flume-ng." }, "affects": [ { "ref": "pkg:maven/org.apache.logging.log4j/log4j-flume-ng@2.22.1-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:70f2f04e-899f-55ff-b8b8-2b133c28f044", "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-flume-ng. 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-flume-ng@2.22.1-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:e02f6db5-bc75-59c1-ae98-ebce6f80d228", "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-flume-ng." }, "affects": [ { "ref": "pkg:maven/org.apache.logging.log4j/log4j-flume-ng@2.22.1-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:914fb28d-f530-5e42-a7e6-6064d25eba1c", "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-flume-ng." }, "affects": [ { "ref": "pkg:maven/org.apache.logging.log4j/log4j-flume-ng@2.22.1-tuxcare.3" } ] } ], "dependencies": [ { "ref": "pkg:maven/org.apache.logging.log4j/log4j-flume-ng@2.22.1-tuxcare.3" } ] }