{ "@id": "urn:uuid:e95f253a-5c9d-4d13-badf-7515b2449688", "role": "Document Creator", "author": "https://tuxcare.com", "version": 38, "@context": "https://openvex.dev/ns/v0.2.0", "timestamp": "2026-10-29T07:42:31.773838+00:00", "statements": [ { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-29T07:42:31.773838+00:00", "status_notes": "Vulnerability CVE-2008-1947 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2008-1947" }, "action_statement": "Vulnerability CVE-2008-1947 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-29T07:42:31.773838+00:00", "status_notes": "Vulnerability CVE-2014-0095 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2014-0095" }, "action_statement": "Vulnerability CVE-2014-0095 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-29T02:36:49.908127+00:00", "status_notes": "Vulnerability CVE-2016-0762 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2016-0762" }, "action_statement": "Vulnerability CVE-2016-0762 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-28T23:28:44.006786+00:00", "status_notes": "Vulnerability CVE-2016-5018 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2016-5018" }, "action_statement": "Vulnerability CVE-2016-5018 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-29T04:08:51.772780+00:00", "status_notes": "Vulnerability CVE-2016-5388 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2016-5388" }, "action_statement": "Vulnerability CVE-2016-5388 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-29T02:36:49.908127+00:00", "status_notes": "Vulnerability CVE-2016-6794 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2016-6794" }, "action_statement": "Vulnerability CVE-2016-6794 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-29T02:36:49.908127+00:00", "status_notes": "Vulnerability CVE-2016-6796 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2016-6796" }, "action_statement": "Vulnerability CVE-2016-6796 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-29T02:36:49.908127+00:00", "status_notes": "Vulnerability CVE-2016-6797 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2016-6797" }, "action_statement": "Vulnerability CVE-2016-6797 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-29T04:08:51.772780+00:00", "status_notes": "Vulnerability CVE-2016-6816 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2016-6816" }, "action_statement": "Vulnerability CVE-2016-6816 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-29T04:08:51.772780+00:00", "status_notes": "Vulnerability CVE-2016-8735 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2016-8735" }, "action_statement": "Vulnerability CVE-2016-8735 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-29T04:08:51.772780+00:00", "status_notes": "Vulnerability CVE-2016-8745 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2016-8745" }, "action_statement": "Vulnerability CVE-2016-8745 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-28T23:37:14.382670+00:00", "status_notes": "Vulnerability CVE-2017-12615 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2017-12615" }, "action_statement": "Vulnerability CVE-2017-12615 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-29T04:08:51.772780+00:00", "status_notes": "Vulnerability CVE-2017-12616 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2017-12616" }, "action_statement": "Vulnerability CVE-2017-12616 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-28T23:28:44.006786+00:00", "status_notes": "Vulnerability CVE-2017-12617 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2017-12617" }, "action_statement": "Vulnerability CVE-2017-12617 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-29T02:36:49.908127+00:00", "status_notes": "Vulnerability CVE-2017-5647 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2017-5647" }, "action_statement": "Vulnerability CVE-2017-5647 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-28T23:28:44.006786+00:00", "status_notes": "Vulnerability CVE-2017-5648 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2017-5648" }, "action_statement": "Vulnerability CVE-2017-5648 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-29T07:42:31.773838+00:00", "status_notes": "Vulnerability CVE-2017-5651 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2017-5651" }, "action_statement": "Vulnerability CVE-2017-5651 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-29T02:36:49.908127+00:00", "status_notes": "Vulnerability CVE-2017-5664 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2017-5664" }, "action_statement": "Vulnerability CVE-2017-5664 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-29T02:36:49.908127+00:00", "status_notes": "Vulnerability CVE-2017-7674 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2017-7674" }, "action_statement": "Vulnerability CVE-2017-7674 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-28T23:37:14.382670+00:00", "status_notes": "Vulnerability CVE-2018-11784 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2018-11784" }, "action_statement": "Vulnerability CVE-2018-11784 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-28T23:28:44.006786+00:00", "status_notes": "Vulnerability CVE-2018-1304 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2018-1304" }, "action_statement": "Vulnerability CVE-2018-1304 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-28T23:41:42.084809+00:00", "status_notes": "Vulnerability CVE-2018-1305 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2018-1305" }, "action_statement": "Vulnerability CVE-2018-1305 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-28T23:28:44.006786+00:00", "status_notes": "Vulnerability CVE-2018-1336 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2018-1336" }, "action_statement": "Vulnerability CVE-2018-1336 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-28T23:28:44.006786+00:00", "status_notes": "Vulnerability CVE-2018-8014 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2018-8014" }, "action_statement": "Vulnerability CVE-2018-8014 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-28T23:28:44.006786+00:00", "status_notes": "Vulnerability CVE-2018-8034 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2018-8034" }, "action_statement": "Vulnerability CVE-2018-8034 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-29T00:51:30.888148+00:00", "status_notes": "Vulnerability CVE-2018-8037 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2018-8037" }, "action_statement": "Vulnerability CVE-2018-8037 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-28T23:28:44.006786+00:00", "status_notes": "Vulnerability CVE-2019-0199 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2019-0199" }, "action_statement": "Vulnerability CVE-2019-0199 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-28T23:37:14.382670+00:00", "status_notes": "Vulnerability CVE-2019-0221 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2019-0221" }, "action_statement": "Vulnerability CVE-2019-0221 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-28T23:28:44.006786+00:00", "status_notes": "Vulnerability CVE-2019-0232 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2019-0232" }, "action_statement": "Vulnerability CVE-2019-0232 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-28T23:59:58.436178+00:00", "status_notes": "Vulnerability CVE-2019-10072 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2019-10072" }, "action_statement": "Vulnerability CVE-2019-10072 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-28T23:28:44.006786+00:00", "status_notes": "Vulnerability CVE-2019-12418 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2019-12418" }, "action_statement": "Vulnerability CVE-2019-12418 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-28T23:28:44.006786+00:00", "status_notes": "Vulnerability CVE-2019-17563 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2019-17563" }, "action_statement": "Vulnerability CVE-2019-17563 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-29T07:42:31.773838+00:00", "status_notes": "Vulnerability CVE-2019-17569 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2019-17569" }, "action_statement": "Vulnerability CVE-2019-17569 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-28T23:49:59.024011+00:00", "status_notes": "Vulnerability CVE-2020-11996 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2020-11996" }, "action_statement": "Vulnerability CVE-2020-11996 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-28T23:49:59.024011+00:00", "status_notes": "Vulnerability CVE-2020-13934 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2020-13934" }, "action_statement": "Vulnerability CVE-2020-13934 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-28T23:49:59.024011+00:00", "status_notes": "Vulnerability CVE-2020-13935 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2020-13935" }, "action_statement": "Vulnerability CVE-2020-13935 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-28T23:49:59.024011+00:00", "status_notes": "Vulnerability CVE-2020-13943 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2020-13943" }, "action_statement": "Vulnerability CVE-2020-13943 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-28T23:49:59.024011+00:00", "status_notes": "Vulnerability CVE-2020-17527 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2020-17527" }, "action_statement": "Vulnerability CVE-2020-17527 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-28T23:28:44.006786+00:00", "status_notes": "Vulnerability CVE-2020-1935 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2020-1935" }, "action_statement": "Vulnerability CVE-2020-1935 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-28T23:28:44.006786+00:00", "status_notes": "Vulnerability CVE-2020-1938 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2020-1938" }, "action_statement": "Vulnerability CVE-2020-1938 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-28T23:28:44.006786+00:00", "status_notes": "Vulnerability CVE-2020-9484 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2020-9484" }, "action_statement": "Vulnerability CVE-2020-9484 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-28T23:33:09.807961+00:00", "status_notes": "Vulnerability CVE-2021-24122 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2021-24122" }, "action_statement": "Vulnerability CVE-2021-24122 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-28T23:59:58.436178+00:00", "status_notes": "Vulnerability CVE-2021-25122 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2021-25122" }, "action_statement": "Vulnerability CVE-2021-25122 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-28T23:28:44.006786+00:00", "status_notes": "Vulnerability CVE-2021-25329 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2021-25329" }, "action_statement": "Vulnerability CVE-2021-25329 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-28T23:49:59.024011+00:00", "status_notes": "Vulnerability CVE-2021-30639 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2021-30639" }, "action_statement": "Vulnerability CVE-2021-30639 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-28T23:49:59.024011+00:00", "status_notes": "Vulnerability CVE-2021-30640 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2021-30640" }, "action_statement": "Vulnerability CVE-2021-30640 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-28T21:20:09.538096+00:00", "status_notes": "Vulnerability CVE-2021-33037 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2021-33037" }, "action_statement": "Vulnerability CVE-2021-33037 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-28T23:49:59.024011+00:00", "status_notes": "Vulnerability CVE-2021-41079 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2021-41079" }, "action_statement": "Vulnerability CVE-2021-41079 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-28T21:18:11.261123+00:00", "status_notes": "Vulnerability CVE-2021-42340 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2021-42340" }, "action_statement": "Vulnerability CVE-2021-42340 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-28T21:19:00.657885+00:00", "status_notes": "Vulnerability CVE-2021-43980 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2021-43980" }, "action_statement": "Vulnerability CVE-2021-43980 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-28T21:20:09.538096+00:00", "status_notes": "Vulnerability CVE-2022-23181 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2022-23181" }, "action_statement": "Vulnerability CVE-2022-23181 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-28T23:49:59.024011+00:00", "status_notes": "Vulnerability CVE-2022-25762 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2022-25762" }, "action_statement": "Vulnerability CVE-2022-25762 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-28T21:16:19.887305+00:00", "status_notes": "Vulnerability CVE-2022-29885 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2022-29885" }, "action_statement": "Vulnerability CVE-2022-29885 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-28T21:17:24.242406+00:00", "status_notes": "Vulnerability CVE-2022-34305 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2022-34305" }, "action_statement": "Vulnerability CVE-2022-34305 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-28T21:12:12.887949+00:00", "status_notes": "Vulnerability CVE-2022-42252 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2022-42252" }, "action_statement": "Vulnerability CVE-2022-42252 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-28T21:04:11.478044+00:00", "status_notes": "Vulnerability CVE-2022-45143 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2022-45143" }, "action_statement": "Vulnerability CVE-2022-45143 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-28T21:11:34.688190+00:00", "status_notes": "Vulnerability CVE-2023-24998 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2023-24998" }, "action_statement": "Vulnerability CVE-2023-24998 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-28T21:16:19.887305+00:00", "status_notes": "Vulnerability CVE-2023-28708 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2023-28708" }, "action_statement": "Vulnerability CVE-2023-28708 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-29T01:46:20.750358+00:00", "status_notes": "Vulnerability CVE-2023-28709 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2023-28709" }, "action_statement": "Vulnerability CVE-2023-28709 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-29T07:42:31.773838+00:00", "status_notes": "Vulnerability CVE-2023-34981 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2023-34981" }, "action_statement": "Vulnerability CVE-2023-34981 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-28T21:07:35.663971+00:00", "status_notes": "Vulnerability CVE-2023-41080 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2023-41080" }, "action_statement": "Vulnerability CVE-2023-41080 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-28T18:11:36.374923+00:00", "status_notes": "Vulnerability CVE-2023-42794 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2023-42794" }, "action_statement": "Vulnerability CVE-2023-42794 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs." }, { "status": "not_affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-28T18:25:50.594919+00:00", "status_notes": "Vulnerability CVE-2023-42795 does not affect version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs. not_affected \u2014 CVE-2023-42795 is NOT present in Tomcat 10.1.50. The upstream fix (commit 9375d67106f by Mark Thomas on 2023-10-05) was already included in the upstream release before TuxCare onboarded version 10.1.50. All four affected recycle() methods (Request.java, ApplicationHttpRequest.java, B2CConverter.java, C2BConverter.java) contain the protective try-catch blocks that prevent exceptions from abortin...", "justification": "vulnerable_code_not_present", "vulnerability": { "name": "CVE-2023-42795" }, "impact_statement": "not_affected \u2014 CVE-2023-42795 is NOT present in Tomcat 10.1.50. The upstream fix (commit 9375d67106f by Mark Thomas on 2023-10-05) was already included in the upstream release before TuxCare onboarded version 10.1.50. All four affected recycle() methods (Request.java, ApplicationHttpRequest.java, B2CConverter.java, C2BConverter.java) contain the protective try-catch blocks that prevent exceptions from abortin..." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-28T18:12:53.572239+00:00", "status_notes": "Vulnerability CVE-2023-44487 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2023-44487" }, "action_statement": "Vulnerability CVE-2023-44487 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs." }, { "status": "not_affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-28T19:11:13.689447+00:00", "status_notes": "Vulnerability CVE-2023-45648 does not affect version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs. not_affected \u2014 Target version 10.1.50 is NOT AFFECTED by CVE-2023-45648. The upstream Apache Tomcat 10.1.50 release already contained the fix for improper HTTP trailer header validation. The vulnerability (unvalidated trailer headers enabling request smuggling) is not present because the code includes HttpHeaderParser with proper validation that rejects non-token characters in header names and control charact...", "justification": "vulnerable_code_not_present", "vulnerability": { "name": "CVE-2023-45648" }, "impact_statement": "not_affected \u2014 Target version 10.1.50 is NOT AFFECTED by CVE-2023-45648. The upstream Apache Tomcat 10.1.50 release already contained the fix for improper HTTP trailer header validation. The vulnerability (unvalidated trailer headers enabling request smuggling) is not present because the code includes HttpHeaderParser with proper validation that rejects non-token characters in header names and control charact..." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-28T18:14:49.853815+00:00", "status_notes": "Vulnerability CVE-2023-46589 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2023-46589" }, "action_statement": "Vulnerability CVE-2023-46589 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-28T23:49:59.024011+00:00", "status_notes": "Vulnerability CVE-2024-21733 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2024-21733" }, "action_statement": "Vulnerability CVE-2024-21733 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs." }, { "status": "not_affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-22T14:18:47.009471+00:00", "status_notes": "Vulnerability CVE-2024-23672 does not affect version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs. not_affected \u2014 Apache Tomcat 10.1.50 is not affected by CVE-2024-23672. The vulnerability (incomplete WebSocket connection cleanup leading to resource exhaustion) was fixed in upstream Apache Tomcat 10.1.19 (released February 2024). Since version 10.1.50 was released December 2025 (much later than the fix), it inherently includes the upstream fix. The target code contains all fix components: SESSION_CLOSE_TIM...", "justification": "vulnerable_code_not_present", "vulnerability": { "name": "CVE-2024-23672" }, "impact_statement": "not_affected \u2014 Apache Tomcat 10.1.50 is not affected by CVE-2024-23672. The vulnerability (incomplete WebSocket connection cleanup leading to resource exhaustion) was fixed in upstream Apache Tomcat 10.1.19 (released February 2024). Since version 10.1.50 was released December 2025 (much later than the fix), it inherently includes the upstream fix. The target code contains all fix components: SESSION_CLOSE_TIM..." }, { "status": "not_affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-22T14:18:47.009471+00:00", "status_notes": "Vulnerability CVE-2024-24549 does not affect version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs. Apache Tomcat 10.1.50 is not affected by CVE-2024-24549. The vulnerability affects versions up to 10.1.18, and was fixed by Apache in version 10.1.19. The target version 10.1.50 was onboarded with the upstream vendor fix already present. The fix moves HTTP/2 header validation from the end of header processing to the end of each frame (HEADERS and CONTINUATION), preventing resource exhaustion from processing excessive headers.", "justification": "vulnerable_code_not_present", "vulnerability": { "name": "CVE-2024-24549" }, "impact_statement": "Apache Tomcat 10.1.50 is not affected by CVE-2024-24549. The vulnerability affects versions up to 10.1.18, and was fixed by Apache in version 10.1.19. The target version 10.1.50 was onboarded with the upstream vendor fix already present. The fix moves HTTP/2 header validation from the end of header processing to the end of each frame (HEADERS and CONTINUATION), preventing resource exhaustion from processing excessive headers." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-28T18:12:53.572239+00:00", "status_notes": "Vulnerability CVE-2024-34750 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2024-34750" }, "action_statement": "Vulnerability CVE-2024-34750 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-28T18:12:53.572239+00:00", "status_notes": "Vulnerability CVE-2024-38286 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2024-38286" }, "action_statement": "Vulnerability CVE-2024-38286 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-28T18:11:36.374923+00:00", "status_notes": "Vulnerability CVE-2024-50379 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2024-50379" }, "action_statement": "Vulnerability CVE-2024-50379 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs." }, { "status": "not_affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-22T14:18:47.009471+00:00", "status_notes": "Vulnerability CVE-2024-52316 does not affect version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs. not_affected \u2014 Target is Apache Tomcat 10.1.50. CVE-2024-52316 (Unchecked Error Condition in Jakarta Authentication / JASPIC) affects 10.1.0-M1 through 10.1.30 and is fixed in 10.1.31. The target (10.1.50) already ships the upstream fix natively. The upstream patch (commit acc2f01/7532f9dc, \"If the Jakarta Authentication fails with an exception, set a 500 status\") adds an explicit response.setStatus(SC_INTERNAL_SERVER_ERROR) in the AuthException catch block of AuthenticatorBase.authenticateJaspic(), so a custom ServerAuthContext that throws during validateRequest() can no longer leave the request in a non-failure state (authentication-bypass). That exact fix is present in the target at java/org/apache/catalina/authenticator/AuthenticatorBase.java lines 806-807. git blame attributes those lines to upstream Apache commit acc2f01395f895980f5d8a64573fcc1bade13369 by Mark Thomas , and git show confirms the fix already exists at the upstream 10.1.50 tag (cd6d685800), which is a direct parent of HEAD. No TuxCare backport branch for this CVE targets 10.1.50 (backports exist only for older versions). Verdict: not_affected (upstream vendor fix baked into the shipped version); justification code_not_present. [VC re-run with claude-opus-4-8, prod pin d46bd7a, 2026-09-21; the earlier Sonnet run was parked by the author-verification gate after crediting a TuxCare backport for an upstream fix]", "justification": "vulnerable_code_not_present", "vulnerability": { "name": "CVE-2024-52316" }, "impact_statement": "not_affected \u2014 Target is Apache Tomcat 10.1.50. CVE-2024-52316 (Unchecked Error Condition in Jakarta Authentication / JASPIC) affects 10.1.0-M1 through 10.1.30 and is fixed in 10.1.31. The target (10.1.50) already ships the upstream fix natively. The upstream patch (commit acc2f01/7532f9dc, \"If the Jakarta Authentication fails with an exception, set a 500 status\") adds an explicit response.setStatus(SC_INTERNAL_SERVER_ERROR) in the AuthException catch block of AuthenticatorBase.authenticateJaspic(), so a custom ServerAuthContext that throws during validateRequest() can no longer leave the request in a non-failure state (authentication-bypass). That exact fix is present in the target at java/org/apache/catalina/authenticator/AuthenticatorBase.java lines 806-807. git blame attributes those lines to upstream Apache commit acc2f01395f895980f5d8a64573fcc1bade13369 by Mark Thomas , and git show confirms the fix already exists at the upstream 10.1.50 tag (cd6d685800), which is a direct parent of HEAD. No TuxCare backport branch for this CVE targets 10.1.50 (backports exist only for older versions). Verdict: not_affected (upstream vendor fix baked into the shipped version); justification code_not_present. [VC re-run with claude-opus-4-8, prod pin d46bd7a, 2026-09-21; the earlier Sonnet run was parked by the author-verification gate after crediting a TuxCare backport for an upstream fix]" }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-29T07:42:31.773838+00:00", "status_notes": "Vulnerability CVE-2024-52317 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2024-52317" }, "action_statement": "Vulnerability CVE-2024-52317 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs." }, { "status": "not_affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-28T19:16:24.474096+00:00", "status_notes": "Vulnerability CVE-2024-54677 does not affect version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs. not_affected \u2014 CVE-2024-54677 affects Apache Tomcat's examples web application (SessionExample servlet) through uncontrolled resource consumption. The vulnerability allowed unlimited session attributes to be created, exhausting server memory. The target repository version 10.1.50 is not affected because the fix (SESSION_ATTRIBUTE_COUNT_LIMIT = 10) was already present in the upstream Apache Tomcat 10.1.50 rele...", "justification": "vulnerable_code_not_present", "vulnerability": { "name": "CVE-2024-54677" }, "impact_statement": "not_affected \u2014 CVE-2024-54677 affects Apache Tomcat's examples web application (SessionExample servlet) through uncontrolled resource consumption. The vulnerability allowed unlimited session attributes to be created, exhausting server memory. The target repository version 10.1.50 is not affected because the fix (SESSION_ATTRIBUTE_COUNT_LIMIT = 10) was already present in the upstream Apache Tomcat 10.1.50 rele..." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-28T23:49:59.024011+00:00", "status_notes": "Vulnerability CVE-2024-56337 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2024-56337" }, "action_statement": "Vulnerability CVE-2024-56337 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-28T18:14:49.853815+00:00", "status_notes": "Vulnerability CVE-2025-24813 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2025-24813" }, "action_statement": "Vulnerability CVE-2025-24813 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-28T18:12:53.572239+00:00", "status_notes": "Vulnerability CVE-2025-31650 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2025-31650" }, "action_statement": "Vulnerability CVE-2025-31650 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-28T18:12:53.572239+00:00", "status_notes": "Vulnerability CVE-2025-31651 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2025-31651" }, "action_statement": "Vulnerability CVE-2025-31651 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-28T18:14:49.853815+00:00", "status_notes": "Vulnerability CVE-2025-46701 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2025-46701" }, "action_statement": "Vulnerability CVE-2025-46701 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs." }, { "status": "not_affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-22T14:18:47.009471+00:00", "status_notes": "Vulnerability CVE-2025-48988 does not affect version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs. CVE-2025-48988 is NOT present in Apache Tomcat 10.1.50. The upstream fix that adds maxPartCount and maxPartHeaderSize limits to prevent resource exhaustion during multipart request processing is already present in the target version. The fix was authored by Mark Thomas (Apache upstream) in commit cdde8e655bc1c5c60a07efd216251d77c52fd7f6 and is part of the 10.1.50 release.", "justification": "vulnerable_code_not_present", "vulnerability": { "name": "CVE-2025-48988" }, "impact_statement": "CVE-2025-48988 is NOT present in Apache Tomcat 10.1.50. The upstream fix that adds maxPartCount and maxPartHeaderSize limits to prevent resource exhaustion during multipart request processing is already present in the target version. The fix was authored by Mark Thomas (Apache upstream) in commit cdde8e655bc1c5c60a07efd216251d77c52fd7f6 and is part of the 10.1.50 release." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-28T18:11:36.374923+00:00", "status_notes": "Vulnerability CVE-2025-48989 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2025-48989" }, "action_statement": "Vulnerability CVE-2025-48989 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-28T18:12:53.572239+00:00", "status_notes": "Vulnerability CVE-2025-49124 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2025-49124" }, "action_statement": "Vulnerability CVE-2025-49124 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs." }, { "status": "not_affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-22T14:18:47.009471+00:00", "status_notes": "Vulnerability CVE-2025-49125 does not affect version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs. Target version 10.1.50 already contains the upstream Apache Tomcat fix for CVE-2025-49125. The vulnerable path.startsWith(webAppMount) pattern has been replaced with the secure isPathMounted() method that enforces proper path boundary checking. The fix was authored by Mark Thomas (markt@apache.org) in upstream commit 7617b9c247bc77ed0444dd69adcd8aa48777886c and was included in upstream version 10.1.42. Since 10.1.50 > 10.1.42, the fix was already present when TuxCare onboarded this version.", "justification": "vulnerable_code_not_present", "vulnerability": { "name": "CVE-2025-49125" }, "impact_statement": "Target version 10.1.50 already contains the upstream Apache Tomcat fix for CVE-2025-49125. The vulnerable path.startsWith(webAppMount) pattern has been replaced with the secure isPathMounted() method that enforces proper path boundary checking. The fix was authored by Mark Thomas (markt@apache.org) in upstream commit 7617b9c247bc77ed0444dd69adcd8aa48777886c and was included in upstream version 10.1.42. Since 10.1.50 > 10.1.42, the fix was already present when TuxCare onboarded this version." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-28T18:14:49.853815+00:00", "status_notes": "Vulnerability CVE-2025-52434 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2025-52434" }, "action_statement": "Vulnerability CVE-2025-52434 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-28T18:14:49.853815+00:00", "status_notes": "Vulnerability CVE-2025-52520 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2025-52520" }, "action_statement": "Vulnerability CVE-2025-52520 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-28T18:12:53.572239+00:00", "status_notes": "Vulnerability CVE-2025-53506 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2025-53506" }, "action_statement": "Vulnerability CVE-2025-53506 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs." }, { "status": "not_affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-28T20:40:53.651459+00:00", "status_notes": "Vulnerability CVE-2025-55668 does not affect version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs. not_affected \u2014 Target Apache Tomcat 10.1.50-tuxcare.2 is not affected by CVE-2025-55668. The vulnerability was fixed in upstream Apache Tomcat 10.1.42, and the target version 10.1.50 already contains the complete upstream fix. The fix (commit 8621e4c6ba by remm@apache.org) was shipped in the upstream 10.1.50 release that TuxCare onboarded, not backported by TuxCare. Both critical components of the fix are pre...", "justification": "vulnerable_code_not_present", "vulnerability": { "name": "CVE-2025-55668" }, "impact_statement": "not_affected \u2014 Target Apache Tomcat 10.1.50-tuxcare.2 is not affected by CVE-2025-55668. The vulnerability was fixed in upstream Apache Tomcat 10.1.42, and the target version 10.1.50 already contains the complete upstream fix. The fix (commit 8621e4c6ba by remm@apache.org) was shipped in the upstream 10.1.50 release that TuxCare onboarded, not backported by TuxCare. Both critical components of the fix are pre..." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-28T18:12:53.572239+00:00", "status_notes": "Vulnerability CVE-2025-55752 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2025-55752" }, "action_statement": "Vulnerability CVE-2025-55752 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-28T18:11:01.360398+00:00", "status_notes": "Vulnerability CVE-2025-55754 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2025-55754" }, "action_statement": "Vulnerability CVE-2025-55754 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs." }, { "status": "not_affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-28T19:18:45.160348+00:00", "status_notes": "Vulnerability CVE-2025-61795 does not affect version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs. not_affected \u2014 The target Tomcat 10.1.50 is NOT AFFECTED by CVE-2025-61795. The vulnerability (temporary file accumulation from failed multipart uploads) has been fixed by upstream Apache Tomcat. The fix commit af6e918162 by Mark Thomas (markt@apache.org) was included in the upstream 10.1.50 release that TuxCare onboarded. The CVE states versions 10.1.47+ are fixed, and 10.1.50 meets this requirement. The def...", "justification": "vulnerable_code_not_present", "vulnerability": { "name": "CVE-2025-61795" }, "impact_statement": "not_affected \u2014 The target Tomcat 10.1.50 is NOT AFFECTED by CVE-2025-61795. The vulnerability (temporary file accumulation from failed multipart uploads) has been fixed by upstream Apache Tomcat. The fix commit af6e918162 by Mark Thomas (markt@apache.org) was included in the upstream 10.1.50 release that TuxCare onboarded. The CVE states versions 10.1.47+ are fixed, and 10.1.50 meets this requirement. The def..." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-28T18:11:01.360398+00:00", "status_notes": "Vulnerability CVE-2025-66614 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2025-66614" }, "action_statement": "Vulnerability CVE-2025-66614 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs." }, { "status": "not_affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-28T18:59:36.443819+00:00", "status_notes": "Vulnerability CVE-2026-24733 does not affect version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs. not_affected \u2014 Apache Tomcat 10.1.50 is NOT affected by CVE-2026-24733. The vulnerability (accepting non-GET HTTP methods for HTTP/0.9 requests) is not present in the target. The upstream fix authored by remm@apache.org (commit 711b465cf2) was already included in the Apache Tomcat 10.1.50 release that TuxCare onboarded. The defense validates that HTTP/0.9 requests use only the GET method and rejects all other...", "justification": "vulnerable_code_not_present", "vulnerability": { "name": "CVE-2026-24733" }, "impact_statement": "not_affected \u2014 Apache Tomcat 10.1.50 is NOT affected by CVE-2026-24733. The vulnerability (accepting non-GET HTTP methods for HTTP/0.9 requests) is not present in the target. The upstream fix authored by remm@apache.org (commit 711b465cf2) was already included in the Apache Tomcat 10.1.50 release that TuxCare onboarded. The defense validates that HTTP/0.9 requests use only the GET method and rejects all other..." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-22T14:18:47.009471+00:00", "status_notes": "Vulnerability CVE-2026-24734 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2026-24734" }, "action_statement": "Vulnerability CVE-2026-24734 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-23T14:22:56.598523+00:00", "status_notes": "Vulnerability CVE-2026-24880 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs, and is fixed in 10.1.50-tuxcare.2.", "vulnerability": { "name": "CVE-2026-24880" }, "action_statement": "Vulnerability CVE-2026-24880 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs, and is fixed in 10.1.50-tuxcare.2." }, { "status": "fixed", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-22T14:18:56.063006+00:00", "status_notes": "Vulnerability CVE-2026-25854 is fixed in version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2026-25854" } }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-29T07:42:31.773838+00:00", "status_notes": "Vulnerability CVE-2026-29129 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2026-29129" }, "action_statement": "Vulnerability CVE-2026-29129 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-23T14:22:45.375049+00:00", "status_notes": "Vulnerability CVE-2026-29145 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs, and is fixed in 10.1.50-tuxcare.2.", "vulnerability": { "name": "CVE-2026-29145" }, "action_statement": "Vulnerability CVE-2026-29145 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs, and is fixed in 10.1.50-tuxcare.2." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-23T14:22:45.375049+00:00", "status_notes": "Vulnerability CVE-2026-29146 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs, and is fixed in 10.1.50-tuxcare.2.", "vulnerability": { "name": "CVE-2026-29146" }, "action_statement": "Vulnerability CVE-2026-29146 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs, and is fixed in 10.1.50-tuxcare.2." }, { "status": "fixed", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-22T14:18:56.063006+00:00", "status_notes": "Vulnerability CVE-2026-32990 is fixed in version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2026-32990" } }, { "status": "fixed", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-22T14:18:56.063006+00:00", "status_notes": "Vulnerability CVE-2026-34483 is fixed in version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2026-34483" } }, { "status": "fixed", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-22T14:18:56.063006+00:00", "status_notes": "Vulnerability CVE-2026-34487 is fixed in version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2026-34487" } }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-22T14:18:47.009471+00:00", "status_notes": "Vulnerability CVE-2026-34500 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2026-34500" }, "action_statement": "Vulnerability CVE-2026-34500 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs." }, { "status": "fixed", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-22T14:18:56.063006+00:00", "status_notes": "Vulnerability CVE-2026-41284 is fixed in version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2026-41284" } }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-23T14:22:42.813849+00:00", "status_notes": "Vulnerability CVE-2026-41293 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs, and is fixed in 10.1.50-tuxcare.2.", "vulnerability": { "name": "CVE-2026-41293" }, "action_statement": "Vulnerability CVE-2026-41293 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs, and is fixed in 10.1.50-tuxcare.2." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-23T14:22:42.813849+00:00", "status_notes": "Vulnerability CVE-2026-42498 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs, and is fixed in 10.1.50-tuxcare.2.", "vulnerability": { "name": "CVE-2026-42498" }, "action_statement": "Vulnerability CVE-2026-42498 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs, and is fixed in 10.1.50-tuxcare.2." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-22T14:18:47.009471+00:00", "status_notes": "Vulnerability CVE-2026-43512 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2026-43512" }, "action_statement": "Vulnerability CVE-2026-43512 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-23T14:22:42.813849+00:00", "status_notes": "Vulnerability CVE-2026-43513 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs, and is fixed in 10.1.50-tuxcare.2.", "vulnerability": { "name": "CVE-2026-43513" }, "action_statement": "Vulnerability CVE-2026-43513 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs, and is fixed in 10.1.50-tuxcare.2." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-22T14:18:47.009471+00:00", "status_notes": "Vulnerability CVE-2026-43514 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2026-43514" }, "action_statement": "Vulnerability CVE-2026-43514 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-22T14:18:47.009471+00:00", "status_notes": "Vulnerability CVE-2026-43515 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2026-43515" }, "action_statement": "Vulnerability CVE-2026-43515 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-23T21:50:56.656209+00:00", "status_notes": "Vulnerability CVE-2026-53434 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2026-53434" }, "action_statement": "Vulnerability CVE-2026-53434 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs." }, { "status": "fixed", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-22T14:19:06.974429+00:00", "status_notes": "Vulnerability CVE-2026-65182 is fixed in version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2026-65182" } }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-29T00:29:56.875680+00:00", "status_notes": "Vulnerability CVE-2026-65637 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2026-65637" }, "action_statement": "Vulnerability CVE-2026-65637 affects version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs." }, { "status": "fixed", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-22T14:19:06.974429+00:00", "status_notes": "Vulnerability CVE-2026-65905 is fixed in version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2026-65905" } }, { "status": "fixed", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-22T14:19:06.974429+00:00", "status_notes": "Vulnerability CVE-2026-68525 is fixed in version 10.1.50-tuxcare.1 of org.apache.tomcat:tomcat-i18n-cs.", "vulnerability": { "name": "CVE-2026-68525" } }, { "status": "not_affected", "products": [ { "@id": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.apache.tomcat/tomcat-i18n-cs@10.1.50-tuxcare.1" } } ], "timestamp": "2026-10-29T07:42:31.773838+00:00", "status_notes": "Vulnerability GHSA-r53m-pfr5-7v87 is a false positive for org.apache.tomcat:tomcat-i18n-cs 10.1.50-tuxcare.1.", "vulnerability": { "name": "GHSA-r53m-pfr5-7v87" }, "impact_statement": "The vulnerability has been withdrawn." } ] }