{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:eae4bf0d-7adb-5670-92b5-d81ad5d85012", "version": 1, "metadata": { "tools": [ { "name": "tuxcare-vex-generator", "version": "1.0.0" } ] }, "components": [ { "bom-ref": "pkg:maven/org.apache.tomcat/tomcat-i18n-ja@9.0.83-tuxcare.4", "type": "library", "group": "org.apache.tomcat", "name": "tomcat-i18n-ja", "version": "9.0.83-tuxcare.4", "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-ja@9.0.83-tuxcare.4" } ], "vulnerabilities": [ { "bom-ref": "urn:uuid:61ee1334-77e7-5c11-8d3e-7393e875463f", "id": "CVE-2020-11996", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2020-11996 does not affect version 9.0.83-tuxcare.4 of org.apache.tomcat:tomcat-i18n-ja. Apache Tomcat 9.0.83 is not affected by CVE-2020-11996. The vulnerability (high CPU usage from inefficient iteration over large HTTP/2 stream ID gaps) was fixed upstream in commit 9a0231683a, Fix BZ 64467 Improve performance of closing idle streams, which shipped in Tomcat 9.0.36 in June 2020. The target version 9.0.83 naturally includes this upstream vendor fix. The vulnerable sequential iteration through stream IDs has been replaced with an optimized ConcurrentNavigableMap.subMap() approach in Http2UpgradeHandler.closeIdleStreams that only iterates over actually-existing streams, preventing CPU exhaustion attacks. The CVE affected versions 9.0.0.M1 to 9.0.35; version 9.0.83 is well beyond the affected range." }, "affects": [ { "ref": "pkg:maven/org.apache.tomcat/tomcat-i18n-ja@9.0.83-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:3ce3fec8-b936-5416-bcde-d75f5a1cfaa6", "id": "CVE-2020-13934", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2020-13934 does not affect version 9.0.83-tuxcare.4 of org.apache.tomcat:tomcat-i18n-ja. CVE-2020-13934 is not present in Tomcat 9.0.83-tuxcare.5. The vulnerability affects Tomcat 9.0.0.M5 to 9.0.36 where h2c direct connections did not release the HTTP/1.1 processor after upgrading to HTTP/2, causing memory exhaustion. The upstream Apache fix (commit 172977f0 by Mark Thomas, released in 9.0.37) that adds release(processor) before creating the upgrade processor is already present in the target at AbstractProtocol.java lines 945-946. Since version 9.0.83 is well after the affected range and inherits the vendor fix from upstream, the target is not affected." }, "affects": [ { "ref": "pkg:maven/org.apache.tomcat/tomcat-i18n-ja@9.0.83-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:8e34feb9-3955-5e29-bf86-b935db680efd", "id": "CVE-2020-13943", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2020-13943 does not affect version 9.0.83-tuxcare.4 of org.apache.tomcat:tomcat-i18n-ja. not_affected \u2014 CVE-2020-13943 is NOT present in Apache Tomcat 9.0.83-tuxcare.5. The vulnerability affected Tomcat versions up to 9.0.37 and was fixed in 9.0.38 (July 2020) by upstream Apache. The target version 9.0.83 is based on the upstream Apache Tomcat 9.0.83 release (November 2023), which already contains the fix. The concurrent stream limit check has been correctly moved from headersStart() to headersEn..." }, "affects": [ { "ref": "pkg:maven/org.apache.tomcat/tomcat-i18n-ja@9.0.83-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:563e1367-cea5-5441-b13a-5dd2a62475cf", "id": "CVE-2020-9484", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2020-9484 does not affect version 9.0.83-tuxcare.4 of org.apache.tomcat:tomcat-i18n-ja. Apache Tomcat 9.0.83 is not affected by CVE-2020-9484. The vulnerability (path traversal in session ID allowing arbitrary file deserialization) was fixed by upstream Apache in commit 3aa8f28db7e (Mark Thomas, May 2020) before version 9.0.83 was released. The fix validates that session file paths remain within the storage directory using canonical path comparison. CVE-2020-9484 affected versions 9.0.0.M1 to 9.0.34; version 9.0.83 was released later with the fix already present in the upstream codebase." }, "affects": [ { "ref": "pkg:maven/org.apache.tomcat/tomcat-i18n-ja@9.0.83-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:20227d81-fadc-50cf-bb41-aef019fbf72b", "id": "CVE-2021-24122", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2021-24122 does not affect version 9.0.83-tuxcare.4 of org.apache.tomcat:tomcat-i18n-ja. CVE-2021-24122 affects Apache Tomcat 9.0.0.M1-9.0.39" }, "affects": [ { "ref": "pkg:maven/org.apache.tomcat/tomcat-i18n-ja@9.0.83-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:7086a7f1-f74e-5b84-99e4-b088f264056d", "id": "CVE-2021-42340", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2021-42340 does not affect version 9.0.83-tuxcare.4 of org.apache.tomcat:tomcat-i18n-ja. The target Apache Tomcat 9.0.83-tuxcare.5 is NOT vulnerable to CVE-2021-42340. The memory leak vulnerability affecting WebSocket connections was fixed by upstream Apache in commit 80f1438ec45 (2021-09-27) and is already present in the base Apache Tomcat 9.0.83 release (2023-11-09) that TuxCare's version is built upon. The vulnerable code pattern (missing WebConnection storage and cleanup) does not exist in the target. The fix properly stores the WebConnection reference during init() and closes/nulls it in destroy(), preventing the memory leak." }, "affects": [ { "ref": "pkg:maven/org.apache.tomcat/tomcat-i18n-ja@9.0.83-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:0c540fd0-a37b-5cd0-9e6b-336f9cbddda2", "id": "CVE-2022-34305", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2022-34305 does not affect version 9.0.83-tuxcare.4 of org.apache.tomcat:tomcat-i18n-ja. not_affected \u2014 fixed upstream before 9.0.83: CVE-2022-34305 fix 8b60af90b999 by markt@apache.org (2022-06-23) is an ancestor of tuxcare-current/9.0.83 (inside upstream tag 9.0.83); no TuxCare backport for this CVE on the branch \u2014 the CloudLinux commits VC credited are backports for other CVEs on the same branch. Manual re-label of VC verdict already_fixed\u2192not_affected after git verification, 2026-09-11." }, "affects": [ { "ref": "pkg:maven/org.apache.tomcat/tomcat-i18n-ja@9.0.83-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:c5a71270-ac88-500e-a5ea-1f294b28a450", "id": "CVE-2022-45143", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2022-45143 does not affect version 9.0.83-tuxcare.4 of org.apache.tomcat:tomcat-i18n-ja. Apache Tomcat 9.0.83 is not affected by CVE-2022-45143. The upstream Apache fix (commit b336f4e58893ea35114f1e4a415657f723b1298e by Mark Thomas) was already present in the upstream 9.0.83 release, which serves as the base for this TuxCare branch. The JsonErrorReportValve properly escapes type, message, and description fields using JSONFilter.escape() before embedding them in JSON output, preventing the JSON injection vulnerability. The CVE affects versions 9.0.40 to 9.0.68; this version (9.0.83) is outside the affected range." }, "affects": [ { "ref": "pkg:maven/org.apache.tomcat/tomcat-i18n-ja@9.0.83-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:1e428cde-710b-5539-9929-88a6713ced13", "id": "CVE-2024-23672", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-23672 is fixed in version 9.0.83-tuxcare.4 of org.apache.tomcat:tomcat-i18n-ja." }, "affects": [ { "ref": "pkg:maven/org.apache.tomcat/tomcat-i18n-ja@9.0.83-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:283987e2-0679-569c-9282-3d1d20b8a629", "id": "CVE-2024-24549", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-24549 is fixed in version 9.0.83-tuxcare.4 of org.apache.tomcat:tomcat-i18n-ja." }, "affects": [ { "ref": "pkg:maven/org.apache.tomcat/tomcat-i18n-ja@9.0.83-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:6614eabc-ecbc-5684-ab1c-aa9abf0e91a6", "id": "CVE-2024-34750", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-34750 is fixed in version 9.0.83-tuxcare.4 of org.apache.tomcat:tomcat-i18n-ja." }, "affects": [ { "ref": "pkg:maven/org.apache.tomcat/tomcat-i18n-ja@9.0.83-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:2d348f88-f429-528f-8ad3-f0f7d3926498", "id": "CVE-2024-38286", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-38286 is fixed in version 9.0.83-tuxcare.4 of org.apache.tomcat:tomcat-i18n-ja." }, "affects": [ { "ref": "pkg:maven/org.apache.tomcat/tomcat-i18n-ja@9.0.83-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:d6329365-3fc0-5833-acf5-834c1e661e45", "id": "CVE-2024-50379", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-50379 is fixed in version 9.0.83-tuxcare.4 of org.apache.tomcat:tomcat-i18n-ja." }, "affects": [ { "ref": "pkg:maven/org.apache.tomcat/tomcat-i18n-ja@9.0.83-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:1f64d235-05e9-536e-8321-b673bddfd720", "id": "CVE-2024-52316", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-52316 is fixed in version 9.0.83-tuxcare.4 of org.apache.tomcat:tomcat-i18n-ja." }, "affects": [ { "ref": "pkg:maven/org.apache.tomcat/tomcat-i18n-ja@9.0.83-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:8e4e6024-840e-5f52-be6e-f5d872745994", "id": "CVE-2024-54677", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-54677 is fixed in version 9.0.83-tuxcare.4 of org.apache.tomcat:tomcat-i18n-ja." }, "affects": [ { "ref": "pkg:maven/org.apache.tomcat/tomcat-i18n-ja@9.0.83-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:540e1554-3535-5ac9-8899-9ba2b3fa3e26", "id": "CVE-2024-56337", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-56337 is fixed in version 9.0.83-tuxcare.4 of org.apache.tomcat:tomcat-i18n-ja." }, "affects": [ { "ref": "pkg:maven/org.apache.tomcat/tomcat-i18n-ja@9.0.83-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:1b45fa15-9a9d-58b5-9412-0869f938b467", "id": "CVE-2025-24813", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-24813 is fixed in version 9.0.83-tuxcare.4 of org.apache.tomcat:tomcat-i18n-ja." }, "affects": [ { "ref": "pkg:maven/org.apache.tomcat/tomcat-i18n-ja@9.0.83-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:bb346805-d2a4-559b-bcf1-19f085e97eca", "id": "CVE-2025-31650", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-31650 is fixed in version 9.0.83-tuxcare.4 of org.apache.tomcat:tomcat-i18n-ja." }, "affects": [ { "ref": "pkg:maven/org.apache.tomcat/tomcat-i18n-ja@9.0.83-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:6ab81636-14d9-5674-99bd-e6e19722b245", "id": "CVE-2025-31651", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-31651 is fixed in version 9.0.83-tuxcare.4 of org.apache.tomcat:tomcat-i18n-ja." }, "affects": [ { "ref": "pkg:maven/org.apache.tomcat/tomcat-i18n-ja@9.0.83-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:33efd109-1a2f-5eb9-8c9e-51e997b9be6e", "id": "CVE-2025-46701", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-46701 is fixed in version 9.0.83-tuxcare.4 of org.apache.tomcat:tomcat-i18n-ja." }, "affects": [ { "ref": "pkg:maven/org.apache.tomcat/tomcat-i18n-ja@9.0.83-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:f96405e1-16d5-5c3b-b8ea-4f774a0413e4", "id": "CVE-2025-48988", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-48988 is fixed in version 9.0.83-tuxcare.4 of org.apache.tomcat:tomcat-i18n-ja." }, "affects": [ { "ref": "pkg:maven/org.apache.tomcat/tomcat-i18n-ja@9.0.83-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:8a7a970b-eaa5-54e8-99d8-05603cc416f0", "id": "CVE-2025-48989", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-48989 is fixed in version 9.0.83-tuxcare.4 of org.apache.tomcat:tomcat-i18n-ja." }, "affects": [ { "ref": "pkg:maven/org.apache.tomcat/tomcat-i18n-ja@9.0.83-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:dc3bb3ea-7a47-5cac-b8a9-57d73118f643", "id": "CVE-2025-49124", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-49124 is fixed in version 9.0.83-tuxcare.4 of org.apache.tomcat:tomcat-i18n-ja." }, "affects": [ { "ref": "pkg:maven/org.apache.tomcat/tomcat-i18n-ja@9.0.83-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:cc1b2548-425d-5cba-9bfb-e49b0c57bd45", "id": "CVE-2025-49125", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-49125 is fixed in version 9.0.83-tuxcare.4 of org.apache.tomcat:tomcat-i18n-ja." }, "affects": [ { "ref": "pkg:maven/org.apache.tomcat/tomcat-i18n-ja@9.0.83-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:aa4eedd7-4d30-5782-8dcf-a0aad89775b2", "id": "CVE-2025-52434", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-52434 is fixed in version 9.0.83-tuxcare.4 of org.apache.tomcat:tomcat-i18n-ja." }, "affects": [ { "ref": "pkg:maven/org.apache.tomcat/tomcat-i18n-ja@9.0.83-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:28d7e00c-f794-557e-9518-ea238201a456", "id": "CVE-2025-52520", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-52520 is fixed in version 9.0.83-tuxcare.4 of org.apache.tomcat:tomcat-i18n-ja." }, "affects": [ { "ref": "pkg:maven/org.apache.tomcat/tomcat-i18n-ja@9.0.83-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:da50b326-74e8-5447-a2c7-b9cade1fdb0a", "id": "CVE-2025-53506", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-53506 is fixed in version 9.0.83-tuxcare.4 of org.apache.tomcat:tomcat-i18n-ja." }, "affects": [ { "ref": "pkg:maven/org.apache.tomcat/tomcat-i18n-ja@9.0.83-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:f114462b-8b2d-5d69-88e3-513557f55352", "id": "CVE-2025-55668", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-55668 is fixed in version 9.0.83-tuxcare.4 of org.apache.tomcat:tomcat-i18n-ja." }, "affects": [ { "ref": "pkg:maven/org.apache.tomcat/tomcat-i18n-ja@9.0.83-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:67b80cd3-cddc-581d-be68-656b48f0ed66", "id": "CVE-2025-55752", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-55752 affects version 9.0.83-tuxcare.4 of org.apache.tomcat:tomcat-i18n-ja." }, "affects": [ { "ref": "pkg:maven/org.apache.tomcat/tomcat-i18n-ja@9.0.83-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:a399d67b-b9f3-52a3-a214-64f6befb6580", "id": "CVE-2025-55754", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-55754 is fixed in version 9.0.83-tuxcare.4 of org.apache.tomcat:tomcat-i18n-ja." }, "affects": [ { "ref": "pkg:maven/org.apache.tomcat/tomcat-i18n-ja@9.0.83-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:a7175629-988e-54a1-ad77-defeeff7b5aa", "id": "CVE-2025-61795", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-61795 is fixed in version 9.0.83-tuxcare.4 of org.apache.tomcat:tomcat-i18n-ja." }, "affects": [ { "ref": "pkg:maven/org.apache.tomcat/tomcat-i18n-ja@9.0.83-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:e3e09770-4d52-5e08-b678-77a536219bae", "id": "CVE-2025-66614", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-66614 is fixed in version 9.0.83-tuxcare.4 of org.apache.tomcat:tomcat-i18n-ja." }, "affects": [ { "ref": "pkg:maven/org.apache.tomcat/tomcat-i18n-ja@9.0.83-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:71efbaff-888c-55a5-b651-f099a7687e9f", "id": "CVE-2026-24733", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-24733 is fixed in version 9.0.83-tuxcare.4 of org.apache.tomcat:tomcat-i18n-ja." }, "affects": [ { "ref": "pkg:maven/org.apache.tomcat/tomcat-i18n-ja@9.0.83-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:5d0e963f-27b9-5af1-a4ac-4fadf2b42900", "id": "CVE-2026-24734", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-24734 affects version 9.0.83-tuxcare.4 of org.apache.tomcat:tomcat-i18n-ja." }, "affects": [ { "ref": "pkg:maven/org.apache.tomcat/tomcat-i18n-ja@9.0.83-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:6d30f36e-c557-5fc4-a7db-1d86339f2145", "id": "CVE-2026-24880", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-24880 affects version 9.0.83-tuxcare.4 of org.apache.tomcat:tomcat-i18n-ja." }, "affects": [ { "ref": "pkg:maven/org.apache.tomcat/tomcat-i18n-ja@9.0.83-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:8e7cfd66-99c7-59f8-b844-21193f2ad69a", "id": "CVE-2026-25854", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-25854 affects version 9.0.83-tuxcare.4 of org.apache.tomcat:tomcat-i18n-ja." }, "affects": [ { "ref": "pkg:maven/org.apache.tomcat/tomcat-i18n-ja@9.0.83-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:9f0c1d26-0eba-57f5-ab22-77b1c5e8f787", "id": "CVE-2026-29146", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-29146 affects version 9.0.83-tuxcare.4 of org.apache.tomcat:tomcat-i18n-ja." }, "affects": [ { "ref": "pkg:maven/org.apache.tomcat/tomcat-i18n-ja@9.0.83-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:89b7be2e-596b-5098-90b9-cadc2f75a529", "id": "CVE-2026-32990", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-32990 affects version 9.0.83-tuxcare.4 of org.apache.tomcat:tomcat-i18n-ja." }, "affects": [ { "ref": "pkg:maven/org.apache.tomcat/tomcat-i18n-ja@9.0.83-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:7fcc0f76-debc-549d-b47e-ed748bd0e762", "id": "CVE-2026-34483", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-34483 is fixed in version 9.0.83-tuxcare.4 of org.apache.tomcat:tomcat-i18n-ja." }, "affects": [ { "ref": "pkg:maven/org.apache.tomcat/tomcat-i18n-ja@9.0.83-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:44ec5265-b8a3-5c24-81f9-c26c65477df6", "id": "CVE-2026-34486", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-34486 affects version 9.0.83-tuxcare.4 of org.apache.tomcat:tomcat-i18n-ja." }, "affects": [ { "ref": "pkg:maven/org.apache.tomcat/tomcat-i18n-ja@9.0.83-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:c7b69f5b-bc8b-5664-81fc-c6384ad90e56", "id": "CVE-2026-34487", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-34487 affects version 9.0.83-tuxcare.4 of org.apache.tomcat:tomcat-i18n-ja." }, "affects": [ { "ref": "pkg:maven/org.apache.tomcat/tomcat-i18n-ja@9.0.83-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:5765d42a-76e7-5882-a04a-37cd51a26b80", "id": "CVE-2026-41284", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-41284 affects version 9.0.83-tuxcare.4 of org.apache.tomcat:tomcat-i18n-ja." }, "affects": [ { "ref": "pkg:maven/org.apache.tomcat/tomcat-i18n-ja@9.0.83-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:f8e298c4-f69f-5113-bbb8-4439fe22747e", "id": "CVE-2026-41293", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-41293 affects version 9.0.83-tuxcare.4 of org.apache.tomcat:tomcat-i18n-ja." }, "affects": [ { "ref": "pkg:maven/org.apache.tomcat/tomcat-i18n-ja@9.0.83-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:0bb66f6d-b69c-53f8-94a0-7c6b513ee8fb", "id": "CVE-2026-42498", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-42498 affects version 9.0.83-tuxcare.4 of org.apache.tomcat:tomcat-i18n-ja." }, "affects": [ { "ref": "pkg:maven/org.apache.tomcat/tomcat-i18n-ja@9.0.83-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:682067c0-900f-547e-b1e1-970b758511ee", "id": "CVE-2026-43512", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-43512 affects version 9.0.83-tuxcare.4 of org.apache.tomcat:tomcat-i18n-ja." }, "affects": [ { "ref": "pkg:maven/org.apache.tomcat/tomcat-i18n-ja@9.0.83-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:0ad62ea6-b0d3-5c11-b105-1ff8580dab7f", "id": "CVE-2026-43513", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-43513 affects version 9.0.83-tuxcare.4 of org.apache.tomcat:tomcat-i18n-ja." }, "affects": [ { "ref": "pkg:maven/org.apache.tomcat/tomcat-i18n-ja@9.0.83-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:944315d6-e3d0-5944-9c66-2d40d801415d", "id": "CVE-2026-43514", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-43514 affects version 9.0.83-tuxcare.4 of org.apache.tomcat:tomcat-i18n-ja." }, "affects": [ { "ref": "pkg:maven/org.apache.tomcat/tomcat-i18n-ja@9.0.83-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:144698b9-13ea-51a8-8fd8-a5e36911f7d3", "id": "CVE-2026-43515", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-43515 affects version 9.0.83-tuxcare.4 of org.apache.tomcat:tomcat-i18n-ja." }, "affects": [ { "ref": "pkg:maven/org.apache.tomcat/tomcat-i18n-ja@9.0.83-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:031371ef-41ac-5958-87cf-e05df2807ff8", "id": "CVE-2026-65182", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-65182 affects version 9.0.83-tuxcare.4 of org.apache.tomcat:tomcat-i18n-ja." }, "affects": [ { "ref": "pkg:maven/org.apache.tomcat/tomcat-i18n-ja@9.0.83-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:b19675eb-d649-5be3-a42d-1820989017bd", "id": "CVE-2026-65905", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-65905 affects version 9.0.83-tuxcare.4 of org.apache.tomcat:tomcat-i18n-ja." }, "affects": [ { "ref": "pkg:maven/org.apache.tomcat/tomcat-i18n-ja@9.0.83-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:fb7c358f-26f1-598a-82c6-5cb15e01d925", "id": "CVE-2026-68525", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-68525 affects version 9.0.83-tuxcare.4 of org.apache.tomcat:tomcat-i18n-ja." }, "affects": [ { "ref": "pkg:maven/org.apache.tomcat/tomcat-i18n-ja@9.0.83-tuxcare.4" } ] } ], "dependencies": [ { "ref": "pkg:maven/org.apache.tomcat/tomcat-i18n-ja@9.0.83-tuxcare.4" } ] }