{
  "@id": "urn:uuid:fb026639-3818-4eab-958e-e9821b868513",
  "role": "Document Creator",
  "author": "https://tuxcare.com",
  "version": 47,
  "@context": "https://openvex.dev/ns/v0.2.0",
  "timestamp": "2026-11-05T14:19:54.137004+00:00",
  "statements": [
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.100-tuxcare.3",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.100-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-11-03T16:07:05.916705+00:00",
      "status_notes": "Vulnerability CVE-2014-0095 does not affect version 9.0.100-tuxcare.3 of org.apache.tomcat:tomcat-coyote. not_affected \u2014 CVE-2014-0095 affected Apache Tomcat 8.x before 8.0.4, causing thread consumption DoS when processing AJP requests with Content-Length: 0. The target (Tomcat 9.0.100) is not affected because the upstream fix was already present in the release. The fix (commit 8884dae60ac from March 2014 by markt@apache.org) adds explicit handling for zero-length content in the refillReadBuffer method, preventin...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2014-0095"
      },
      "impact_statement": "not_affected \u2014 CVE-2014-0095 affected Apache Tomcat 8.x before 8.0.4, causing thread consumption DoS when processing AJP requests with Content-Length: 0. The target (Tomcat 9.0.100) is not affected because the upstream fix was already present in the release. The fix (commit 8884dae60ac from March 2014 by markt@apache.org) adds explicit handling for zero-length content in the refillReadBuffer method, preventin..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.100-tuxcare.3",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.100-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-11-05T14:19:54.137004+00:00",
      "status_notes": "Vulnerability CVE-2016-6816 does not affect version 9.0.100-tuxcare.3 of org.apache.tomcat:tomcat-coyote. The upstream fix was released in 9.0.0.M12, and version 9.0.100 is a later release of the same line. Advisories: GitHub GHSA-jc7p-5r39-9477 (fixed in 9.0.0.M12), NVD (last affected 9.0.0-milestone11), CVE record (last affected 9.0.0.M11), Snyk (fixed in 9.0.0.M13).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2016-6816"
      },
      "impact_statement": "The upstream fix was released in 9.0.0.M12, and version 9.0.100 is a later release of the same line. Advisories: GitHub GHSA-jc7p-5r39-9477 (fixed in 9.0.0.M12), NVD (last affected 9.0.0-milestone11), CVE record (last affected 9.0.0.M11), Snyk (fixed in 9.0.0.M13)."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.100-tuxcare.3",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.100-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-11-04T09:20:30.171913+00:00",
      "status_notes": "Vulnerability CVE-2017-5651 does not affect version 9.0.100-tuxcare.3 of org.apache.tomcat:tomcat-coyote. CVE-2017-5651 affected Apache Tomcat 9.0.0.M1 to 9.0.0.M18. The target is Tomcat 9.0.100, which already contains the upstream fix applied by Mark Thomas on March 24, 2017. The fix was shipped in the upstream Apache Tomcat 9.0.100 release (tagged Feb 13, 2025) before TuxCare onboarding. All fix patterns are present: SendfileState tracking (line 262), modified while loop condition (line 265), processSendfile() method (line 1420), and no sendfileData clearing in prepareRequest(). The vulnerable pattern (premature Processor recycling during fast sendfile completion) does not exist in this version.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 9.0.0.M1, < 9.0.0.M19; >= 8.5.0, < 8.5.13; >= 9.0.0.M1, < 9.0.0.M19; >= 8.5.0, < 8.5.13), NVD (= 8.5.0; = 8.5.1; = 8.5.2; = 8.5.3; = 8.5.4; = 8.5.5; = 8.5.6; = 8.5.7; = 8.5.8; = 8.5.9; = 8.5.10; = 8.5.11; = 8.5.12; = 9.0.0-milestone1; = 9.0.0-milestone10; = 9.0.0-milestone11; = 9.0.0-milestone12; = 9.0.0-milestone13; = 9.0.0-milestone14; = 9.0.0-milestone15; = 9.0.0-milestone16; = 9.0.0-milestone17; = 9.0.0-milestone18; = 9.0.0-milestone2; = 9.0.0-milestone3; = 9.0.0-milestone4; = 9.0.0-milestone5; = 9.0.0-milestone6; = 9.0.0-milestone7; = 9.0.0-milestone8; = 9.0.0-milestone9), cve.org (>= 9.0.0.M1, <= 9.0.0.M18; >= 8.5.0, <= 8.5.12), Snyk (>= 8.5.0, < 8.5.13; >= 9-alpha, < 9.0.0.M19; >= 8.5.0, < 8.5.13; >= 9.0.0.M1, < 9.0.0.M19).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2017-5651"
      },
      "impact_statement": "CVE-2017-5651 affected Apache Tomcat 9.0.0.M1 to 9.0.0.M18. The target is Tomcat 9.0.100, which already contains the upstream fix applied by Mark Thomas on March 24, 2017. The fix was shipped in the upstream Apache Tomcat 9.0.100 release (tagged Feb 13, 2025) before TuxCare onboarding. All fix patterns are present: SendfileState tracking (line 262), modified while loop condition (line 265), processSendfile() method (line 1420), and no sendfileData clearing in prepareRequest(). The vulnerable pattern (premature Processor recycling during fast sendfile completion) does not exist in this version.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 9.0.0.M1, < 9.0.0.M19; >= 8.5.0, < 8.5.13; >= 9.0.0.M1, < 9.0.0.M19; >= 8.5.0, < 8.5.13), NVD (= 8.5.0; = 8.5.1; = 8.5.2; = 8.5.3; = 8.5.4; = 8.5.5; = 8.5.6; = 8.5.7; = 8.5.8; = 8.5.9; = 8.5.10; = 8.5.11; = 8.5.12; = 9.0.0-milestone1; = 9.0.0-milestone10; = 9.0.0-milestone11; = 9.0.0-milestone12; = 9.0.0-milestone13; = 9.0.0-milestone14; = 9.0.0-milestone15; = 9.0.0-milestone16; = 9.0.0-milestone17; = 9.0.0-milestone18; = 9.0.0-milestone2; = 9.0.0-milestone3; = 9.0.0-milestone4; = 9.0.0-milestone5; = 9.0.0-milestone6; = 9.0.0-milestone7; = 9.0.0-milestone8; = 9.0.0-milestone9), cve.org (>= 9.0.0.M1, <= 9.0.0.M18; >= 8.5.0, <= 8.5.12), Snyk (>= 8.5.0, < 8.5.13; >= 9-alpha, < 9.0.0.M19; >= 8.5.0, < 8.5.13; >= 9.0.0.M1, < 9.0.0.M19)."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.100-tuxcare.3",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.100-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-11-04T09:15:51.446651+00:00",
      "status_notes": "Vulnerability CVE-2019-0199 does not affect version 9.0.100-tuxcare.3 of org.apache.tomcat:tomcat-coyote. CVE-2019-0199 describes a DoS vulnerability in Apache Tomcat's HTTP/2 implementation (versions 9.0.0.M1-9.0.14 and 8.5.0-8.5.37) where excessive SETTINGS frames and indefinitely blocking streams can exhaust server threads. The target (Tomcat 9.0.100-tuxcare.6) is NOT AFFECTED because all three upstream mitigations are present: (1) stream read timeouts (20s default), (2) stream write timeouts (20s default), and (3) overhead frame tracking that closes connections sending excessive non-data frames. These fixes were committed by Apache upstream (Mark Thomas) on 2019-02-01, included in Tomcat 9.0.15 (March 2019), and were already present in 9.0.100 when TuxCare onboarded it in December 2025. The vulnerable code pattern does not exist in the target because the upstream release already contained the fix.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 9.0.0, < 9.0.16; >= 8.0.0, < 8.5.38; >= 9.0.0, < 9.0.16; >= 8.0.0, < 8.5.38), NVD (>= 8.5.0, <= 8.5.37; >= 9.0.1, <= 9.0.14; = 9.0.0-milestone1; = 9.0.0-milestone10; = 9.0.0-milestone11; = 9.0.0-milestone12; = 9.0.0-milestone13; = 9.0.0-milestone14; = 9.0.0-milestone15; = 9.0.0-milestone16; = 9.0.0-milestone17; = 9.0.0-milestone18; = 9.0.0-milestone19; = 9.0.0-milestone2; = 9.0.0-milestone20; = 9.0.0-milestone21; = 9.0.0-milestone3; = 9.0.0-milestone4; = 9.0.0-milestone5; = 9.0.0-milestone6; = 9.0.0-milestone7; = 9.0.0-milestone8; = 9.0.0-milestone9), cve.org (>= 9.0.0.M1, <= 9.0.14; >= 8.5.0, <= 8.5.37), Snyk (>= 8.5.0, < 8.5.38; >= 9.0.0.M1, < 9.0.16; >= 8.5.0, < 8.5.38; >= 9.0.0.M1, < 9.0.16; >= 8.5.0, < 8.5.38; >= 9.0.0.M1, < 9.0.16).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2019-0199"
      },
      "impact_statement": "CVE-2019-0199 describes a DoS vulnerability in Apache Tomcat's HTTP/2 implementation (versions 9.0.0.M1-9.0.14 and 8.5.0-8.5.37) where excessive SETTINGS frames and indefinitely blocking streams can exhaust server threads. The target (Tomcat 9.0.100-tuxcare.6) is NOT AFFECTED because all three upstream mitigations are present: (1) stream read timeouts (20s default), (2) stream write timeouts (20s default), and (3) overhead frame tracking that closes connections sending excessive non-data frames. These fixes were committed by Apache upstream (Mark Thomas) on 2019-02-01, included in Tomcat 9.0.15 (March 2019), and were already present in 9.0.100 when TuxCare onboarded it in December 2025. The vulnerable code pattern does not exist in the target because the upstream release already contained the fix.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 9.0.0, < 9.0.16; >= 8.0.0, < 8.5.38; >= 9.0.0, < 9.0.16; >= 8.0.0, < 8.5.38), NVD (>= 8.5.0, <= 8.5.37; >= 9.0.1, <= 9.0.14; = 9.0.0-milestone1; = 9.0.0-milestone10; = 9.0.0-milestone11; = 9.0.0-milestone12; = 9.0.0-milestone13; = 9.0.0-milestone14; = 9.0.0-milestone15; = 9.0.0-milestone16; = 9.0.0-milestone17; = 9.0.0-milestone18; = 9.0.0-milestone19; = 9.0.0-milestone2; = 9.0.0-milestone20; = 9.0.0-milestone21; = 9.0.0-milestone3; = 9.0.0-milestone4; = 9.0.0-milestone5; = 9.0.0-milestone6; = 9.0.0-milestone7; = 9.0.0-milestone8; = 9.0.0-milestone9), cve.org (>= 9.0.0.M1, <= 9.0.14; >= 8.5.0, <= 8.5.37), Snyk (>= 8.5.0, < 8.5.38; >= 9.0.0.M1, < 9.0.16; >= 8.5.0, < 8.5.38; >= 9.0.0.M1, < 9.0.16; >= 8.5.0, < 8.5.38; >= 9.0.0.M1, < 9.0.16)."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.100-tuxcare.3",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.100-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2020-13934 does not affect version 9.0.100-tuxcare.3 of org.apache.tomcat:tomcat-coyote. CVE-2020-13934 is not present in Tomcat 9.0.100. The vulnerability (h2c direct connection causing HTTP/1.1 processor leak leading to pool exhaustion) was fixed in upstream Apache Tomcat 9.0.37 (June 30, 2020) via commit 172977f04a authored by Mark Thomas (markt@apache.org). The fix adds release(processor) before creating the h2c upgrade processor and changes control flow to ensure proper cleanup. Since version 9.0.100 (released Feb 13, 2025) is later than 9.0.37, it inherently includes this upstream fix. The vulnerable code pattern is not present in the target.",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2020-13934"
      },
      "impact_statement": "CVE-2020-13934 is not present in Tomcat 9.0.100. The vulnerability (h2c direct connection causing HTTP/1.1 processor leak leading to pool exhaustion) was fixed in upstream Apache Tomcat 9.0.37 (June 30, 2020) via commit 172977f04a authored by Mark Thomas (markt@apache.org). The fix adds release(processor) before creating the h2c upgrade processor and changes control flow to ensure proper cleanup. Since version 9.0.100 (released Feb 13, 2025) is later than 9.0.37, it inherently includes this upstream fix. The vulnerable code pattern is not present in the target."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.100-tuxcare.3",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.100-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2020-13943 does not affect version 9.0.100-tuxcare.3 of org.apache.tomcat:tomcat-coyote. already_fixed \u2014 CVE-2020-13943 has been fixed in this repository. The fix (commit 9d7def063b and backports 55911430df, 1bbc650cbc) moved the max concurrent streams check from headersStart() to headersEnd(), preventing HTTP/2 header confusion when the concurrent streams limit is exceeded.",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2020-13943"
      },
      "impact_statement": "already_fixed \u2014 CVE-2020-13943 has been fixed in this repository. The fix (commit 9d7def063b and backports 55911430df, 1bbc650cbc) moved the max concurrent streams check from headersStart() to headersEnd(), preventing HTTP/2 header confusion when the concurrent streams limit is exceeded."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.100-tuxcare.3",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.100-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-11-04T09:17:29.431970+00:00",
      "status_notes": "Vulnerability CVE-2020-17527 does not affect version 9.0.100-tuxcare.3 of org.apache.tomcat:tomcat-coyote. CVE-2020-17527 (HTTP/2 request header reuse vulnerability) is NOT present in this target. All three upstream fixes for BZ 64830 were already applied by Apache Tomcat before version 9.0.100 was released: (1) HpackDecoder uses local StringBuilder instances instead of a shared field, preventing concurrent access issues; (2) ConnectionSettingsBase uses ConcurrentHashMap instead of EnumMap for thread-safe access; (3) AbstractProtocol properly restores leftover input before processor handoff. The fixes were authored by Mark Thomas (markt@apache.org) in Nov 2020 and Jan 2021, and shipped in the upstream 9.0.100 release that TuxCare onboarded in Dec 2025.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 10.0.0-M1, < 10.0.0-M10; >= 9.0.0-M1, < 9.0.40; >= 8.5.0, < 8.5.60), NVD (>= 8.5.1, <= 8.5.59; >= 9.0.1, <= 9.0.35; = 9.0.0-milestone10; = 9.0.0-milestone11; = 9.0.0-milestone12; = 9.0.0-milestone13; = 9.0.0-milestone14; = 9.0.0-milestone15; = 9.0.0-milestone16; = 9.0.0-milestone17; = 9.0.0-milestone18; = 9.0.0-milestone19; = 9.0.0-milestone20; = 9.0.0-milestone21; = 9.0.0-milestone22; = 9.0.0-milestone23; = 9.0.0-milestone24; = 9.0.0-milestone25; = 9.0.0-milestone26; = 9.0.0-milestone27; = 9.0.0-milestone5; = 9.0.0-milestone6; = 9.0.0-milestone7; = 9.0.0-milestone8; = 9.0.0-milestone9; = 9.0.35-3.39.1; = 9.0.35-3.57.3; = 9.0.36; = 9.0.37; = 9.0.38; = 9.0.39; = 10.0.0-milestone1; = 10.0.0-milestone2; = 10.0.0-milestone3; = 10.0.0-milestone4; = 10.0.0-milestone5; = 10.0.0-milestone6; = 10.0.0-milestone7; = 10.0.0-milestone8; = 10.0.0-milestone9), cve.org (>= 10.0.0-M1, <= 10.0.0-M9; = 10; >= 9.0.0-M1, <= 9.0.39; = 9; >= 8.5.0, <= 8.5.59; = 8.5), Snyk (<= 0; >= 8.5.0, < 8.5.60; >= 9.0.0, < 9.0.40; >= 10.0.0-M1, < 10.0.0-M10).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2020-17527"
      },
      "impact_statement": "CVE-2020-17527 (HTTP/2 request header reuse vulnerability) is NOT present in this target. All three upstream fixes for BZ 64830 were already applied by Apache Tomcat before version 9.0.100 was released: (1) HpackDecoder uses local StringBuilder instances instead of a shared field, preventing concurrent access issues; (2) ConnectionSettingsBase uses ConcurrentHashMap instead of EnumMap for thread-safe access; (3) AbstractProtocol properly restores leftover input before processor handoff. The fixes were authored by Mark Thomas (markt@apache.org) in Nov 2020 and Jan 2021, and shipped in the upstream 9.0.100 release that TuxCare onboarded in Dec 2025.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 10.0.0-M1, < 10.0.0-M10; >= 9.0.0-M1, < 9.0.40; >= 8.5.0, < 8.5.60), NVD (>= 8.5.1, <= 8.5.59; >= 9.0.1, <= 9.0.35; = 9.0.0-milestone10; = 9.0.0-milestone11; = 9.0.0-milestone12; = 9.0.0-milestone13; = 9.0.0-milestone14; = 9.0.0-milestone15; = 9.0.0-milestone16; = 9.0.0-milestone17; = 9.0.0-milestone18; = 9.0.0-milestone19; = 9.0.0-milestone20; = 9.0.0-milestone21; = 9.0.0-milestone22; = 9.0.0-milestone23; = 9.0.0-milestone24; = 9.0.0-milestone25; = 9.0.0-milestone26; = 9.0.0-milestone27; = 9.0.0-milestone5; = 9.0.0-milestone6; = 9.0.0-milestone7; = 9.0.0-milestone8; = 9.0.0-milestone9; = 9.0.35-3.39.1; = 9.0.35-3.57.3; = 9.0.36; = 9.0.37; = 9.0.38; = 9.0.39; = 10.0.0-milestone1; = 10.0.0-milestone2; = 10.0.0-milestone3; = 10.0.0-milestone4; = 10.0.0-milestone5; = 10.0.0-milestone6; = 10.0.0-milestone7; = 10.0.0-milestone8; = 10.0.0-milestone9), cve.org (>= 10.0.0-M1, <= 10.0.0-M9; = 10; >= 9.0.0-M1, <= 9.0.39; = 9; >= 8.5.0, <= 8.5.59; = 8.5), Snyk (<= 0; >= 8.5.0, < 8.5.60; >= 9.0.0, < 9.0.40; >= 10.0.0-M1, < 10.0.0-M10)."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.100-tuxcare.3",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.100-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-11-04T09:17:29.431970+00:00",
      "status_notes": "Vulnerability CVE-2021-25122 does not affect version 9.0.100-tuxcare.3 of org.apache.tomcat:tomcat-coyote. CVE-2021-25122 affects Apache Tomcat 9.0.0.M1 to 9.0.41 where h2c connection upgrades could leak request headers and body data between users. The vulnerability was caused by calling wrapper.unRead(leftOverInput) AFTER creating the new upgrade processor, allowing leftover data to be associated with the wrong connection. The target repository is Apache Tomcat 9.0.100, which already contains the upstream fix (commit d47c20a776) that moves wrapper.unRead() to BEFORE processor creation. This fix was shipped in the upstream Apache Tomcat 9.0.100 release and inherited by TuxCare when they onboarded the version. The vulnerable code pattern is not present in the target.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 10.0.0-M1, < 10.0.2; >= 9.0.0-M1, < 9.0.43; >= 8.5.0, < 8.5.63; >= 10.0.0-M1, < 10.0.2), NVD (>= 8.5.0, <= 8.5.61; >= 9.0.0, <= 9.0.41; = 9.0.0-milestone1; = 9.0.0-milestone10; = 9.0.0-milestone11; = 9.0.0-milestone12; = 9.0.0-milestone13; = 9.0.0-milestone14; = 9.0.0-milestone15; = 9.0.0-milestone16; = 9.0.0-milestone17; = 9.0.0-milestone18; = 9.0.0-milestone19; = 9.0.0-milestone2; = 9.0.0-milestone20; = 9.0.0-milestone21; = 9.0.0-milestone22; = 9.0.0-milestone23; = 9.0.0-milestone24; = 9.0.0-milestone25; = 9.0.0-milestone26; = 9.0.0-milestone27; = 9.0.0-milestone3; = 9.0.0-milestone4; = 9.0.0-milestone5; = 10.0.0; = 10.0.0-milestone1; = 10.0.0-milestone10; = 10.0.0-milestone2; = 10.0.0-milestone3; = 10.0.0-milestone4; = 10.0.0-milestone5; = 10.0.0-milestone6; = 10.0.0-milestone7; = 10.0.0-milestone8; = 10.0.0-milestone9), cve.org (>= 10, < 10.0.2; >= 9, < 9.0.42; >= 8.5, < 8.5.62), Snyk (>= 10.0.0-M1, < 10.0.2; >= 9.0.0.M1, < 9.0.43; >= 8.5.0, < 8.5.63; >= 10.0.0-M1, < 10.0.2; >= 9.0.0.M1, < 9.0.43; >= 8.5.0, < 8.5.63; <= 0).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2021-25122"
      },
      "impact_statement": "CVE-2021-25122 affects Apache Tomcat 9.0.0.M1 to 9.0.41 where h2c connection upgrades could leak request headers and body data between users. The vulnerability was caused by calling wrapper.unRead(leftOverInput) AFTER creating the new upgrade processor, allowing leftover data to be associated with the wrong connection. The target repository is Apache Tomcat 9.0.100, which already contains the upstream fix (commit d47c20a776) that moves wrapper.unRead() to BEFORE processor creation. This fix was shipped in the upstream Apache Tomcat 9.0.100 release and inherited by TuxCare when they onboarded the version. The vulnerable code pattern is not present in the target.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 10.0.0-M1, < 10.0.2; >= 9.0.0-M1, < 9.0.43; >= 8.5.0, < 8.5.63; >= 10.0.0-M1, < 10.0.2), NVD (>= 8.5.0, <= 8.5.61; >= 9.0.0, <= 9.0.41; = 9.0.0-milestone1; = 9.0.0-milestone10; = 9.0.0-milestone11; = 9.0.0-milestone12; = 9.0.0-milestone13; = 9.0.0-milestone14; = 9.0.0-milestone15; = 9.0.0-milestone16; = 9.0.0-milestone17; = 9.0.0-milestone18; = 9.0.0-milestone19; = 9.0.0-milestone2; = 9.0.0-milestone20; = 9.0.0-milestone21; = 9.0.0-milestone22; = 9.0.0-milestone23; = 9.0.0-milestone24; = 9.0.0-milestone25; = 9.0.0-milestone26; = 9.0.0-milestone27; = 9.0.0-milestone3; = 9.0.0-milestone4; = 9.0.0-milestone5; = 10.0.0; = 10.0.0-milestone1; = 10.0.0-milestone10; = 10.0.0-milestone2; = 10.0.0-milestone3; = 10.0.0-milestone4; = 10.0.0-milestone5; = 10.0.0-milestone6; = 10.0.0-milestone7; = 10.0.0-milestone8; = 10.0.0-milestone9), cve.org (>= 10, < 10.0.2; >= 9, < 9.0.42; >= 8.5, < 8.5.62), Snyk (>= 10.0.0-M1, < 10.0.2; >= 9.0.0.M1, < 9.0.43; >= 8.5.0, < 8.5.63; >= 10.0.0-M1, < 10.0.2; >= 9.0.0.M1, < 9.0.43; >= 8.5.0, < 8.5.63; <= 0)."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.100-tuxcare.3",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.100-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-11-03T11:42:00.511362+00:00",
      "status_notes": "Vulnerability CVE-2022-42252 does not affect version 9.0.100-tuxcare.3 of org.apache.tomcat:tomcat-coyote. CVE-2022-42252 affects Apache Tomcat versions 9.0.0-M1 to 9.0.67. The target version 9.0.100 is beyond this range. The fix (commit 4c7f4fd09d) was released in Apache Tomcat 9.0.68 and was already present in the upstream 9.0.100 release that TuxCare onboarded. The vulnerable code pattern (silently accepting malformed Content-Length headers when rejectIllegalHeader=false) is not present in the target. The fix correctly forces rejection of any request with a malformed Content-Length header, preventing HTTP request smuggling attacks.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 8.5.0, < 8.5.83; >= 9.0.0-M1, < 9.0.68; >= 10.0.0-M1, < 10.0.27; >= 10.1.0-M1, < 10.1.1; >= 9.0.0-M1, < 9.0.68; >= 10.0.0-M1, < 10.0.27; >= 10.1.0-M1, < 10.1.1), NVD (>= 8.5.0, < 8.5.83; >= 9.0.0, < 9.0.68; >= 10.0.0, < 10.0.27; >= 10.1.0, < 10.1.1), cve.org (>= 10.1.0-M1, <= 10.1.0; >= 10.0.0-M1, <= 10.0.26; >= 9.0.0-M1, <= 9.0.67; >= 8.5.0, <= 8.5.82), Snyk (>= 8.5.0, < 8.5.53; >= 9.0.0-M1, < 9.0.68; >= 10.0.0-M1, < 10.0.27; >= 10.1.0-M1, < 10.1.1; >= 8.5.0, < 8.5.53; >= 9.0.0-M1, < 9.0.68; >= 10.0.0-M1, < 10.0.27; >= 10.1.0-M1, < 10.1.1).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2022-42252"
      },
      "impact_statement": "CVE-2022-42252 affects Apache Tomcat versions 9.0.0-M1 to 9.0.67. The target version 9.0.100 is beyond this range. The fix (commit 4c7f4fd09d) was released in Apache Tomcat 9.0.68 and was already present in the upstream 9.0.100 release that TuxCare onboarded. The vulnerable code pattern (silently accepting malformed Content-Length headers when rejectIllegalHeader=false) is not present in the target. The fix correctly forces rejection of any request with a malformed Content-Length header, preventing HTTP request smuggling attacks.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 8.5.0, < 8.5.83; >= 9.0.0-M1, < 9.0.68; >= 10.0.0-M1, < 10.0.27; >= 10.1.0-M1, < 10.1.1; >= 9.0.0-M1, < 9.0.68; >= 10.0.0-M1, < 10.0.27; >= 10.1.0-M1, < 10.1.1), NVD (>= 8.5.0, < 8.5.83; >= 9.0.0, < 9.0.68; >= 10.0.0, < 10.0.27; >= 10.1.0, < 10.1.1), cve.org (>= 10.1.0-M1, <= 10.1.0; >= 10.0.0-M1, <= 10.0.26; >= 9.0.0-M1, <= 9.0.67; >= 8.5.0, <= 8.5.82), Snyk (>= 8.5.0, < 8.5.53; >= 9.0.0-M1, < 9.0.68; >= 10.0.0-M1, < 10.0.27; >= 10.1.0-M1, < 10.1.1; >= 8.5.0, < 8.5.53; >= 9.0.0-M1, < 9.0.68; >= 10.0.0-M1, < 10.0.27; >= 10.1.0-M1, < 10.1.1)."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.100-tuxcare.3",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.100-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-11-03T11:41:21.668205+00:00",
      "status_notes": "Vulnerability CVE-2023-24998 does not affect version 9.0.100-tuxcare.3 of org.apache.tomcat:tomcat-coyote. CVE-2023-24998 fix was already present in Apache Tomcat 9.0.100 upstream release. The vulnerability (unbounded multipart request part processing leading to DoS) is not present because commit cf77cc545de by Mark Thomas (Apache) added fileCountMax limiting in December 2022, prior to the 9.0.100 release. Target includes: FileUploadBase.fileCountMax field, setFileCountMax()/getFileCountMax() methods, enforcement check throwing FileCountLimitExceededException when items.size()==fileCountMax, and Request.java calling upload.setFileCountMax(partLimit) with default limit of 10000. The fix is upstream-authored, not a TuxCare backport.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 10.1.0-M1, < 10.1.5; >= 11.0.0-M2, < 11.0.0-M5; >= 8.5.85, < 8.5.88; >= 9.0.0-M1, < 9.0.71; >= 10.1.0-M1, < 10.1.5; >= 11.0.0-M2, < 11.0.0-M5; >= 8.5.85, < 8.5.88; >= 9.0.0-M1, < 9.0.71; >= 10.1.0-M1, < 10.1.5; >= 11.0.0-M2, < 11.0.0-M5; >= 8.5.85, < 8.5.88; >= 9.0.0-M1, < 9.0.71), cve.org (= 11.0.0-M1; >= 10.0.0-M1, <= 10.1.4; >= 9.0.0-M1, <= 9.0.70; >= 8.5.0, <= 8.5.84), Snyk (>= 8.5.0, < 8.5.85; >= 9.0.0-M1, < 9.0.71; >= 10.1.0-M1, < 10.1.5; >= 11.0.0-M1, < 11.0.0-M3; >= 8.5.0, < 8.5.85; >= 9.0.0-M1, < 9.0.71; >= 10.1.0-M1, < 10.1.5; >= 11.0.0-M1, < 11.0.0-M3; >= 8.5.0, < 8.5.85; >= 9.0.0-M1, < 9.0.71; >= 10.1.0-M1, < 10.1.5; >= 11.0.0-M1, < 11.0.0-M3).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2023-24998"
      },
      "impact_statement": "CVE-2023-24998 fix was already present in Apache Tomcat 9.0.100 upstream release. The vulnerability (unbounded multipart request part processing leading to DoS) is not present because commit cf77cc545de by Mark Thomas (Apache) added fileCountMax limiting in December 2022, prior to the 9.0.100 release. Target includes: FileUploadBase.fileCountMax field, setFileCountMax()/getFileCountMax() methods, enforcement check throwing FileCountLimitExceededException when items.size()==fileCountMax, and Request.java calling upload.setFileCountMax(partLimit) with default limit of 10000. The fix is upstream-authored, not a TuxCare backport.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 10.1.0-M1, < 10.1.5; >= 11.0.0-M2, < 11.0.0-M5; >= 8.5.85, < 8.5.88; >= 9.0.0-M1, < 9.0.71; >= 10.1.0-M1, < 10.1.5; >= 11.0.0-M2, < 11.0.0-M5; >= 8.5.85, < 8.5.88; >= 9.0.0-M1, < 9.0.71; >= 10.1.0-M1, < 10.1.5; >= 11.0.0-M2, < 11.0.0-M5; >= 8.5.85, < 8.5.88; >= 9.0.0-M1, < 9.0.71), cve.org (= 11.0.0-M1; >= 10.0.0-M1, <= 10.1.4; >= 9.0.0-M1, <= 9.0.70; >= 8.5.0, <= 8.5.84), Snyk (>= 8.5.0, < 8.5.85; >= 9.0.0-M1, < 9.0.71; >= 10.1.0-M1, < 10.1.5; >= 11.0.0-M1, < 11.0.0-M3; >= 8.5.0, < 8.5.85; >= 9.0.0-M1, < 9.0.71; >= 10.1.0-M1, < 10.1.5; >= 11.0.0-M1, < 11.0.0-M3; >= 8.5.0, < 8.5.85; >= 9.0.0-M1, < 9.0.71; >= 10.1.0-M1, < 10.1.5; >= 11.0.0-M1, < 11.0.0-M3)."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.100-tuxcare.3",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.100-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-11-04T09:18:58.233822+00:00",
      "status_notes": "Vulnerability CVE-2023-28709 does not affect version 9.0.100-tuxcare.3 of org.apache.tomcat:tomcat-coyote. CVE-2023-28709 is NOT present in Tomcat 9.0.100. The vulnerability was an off-by-one error in Parameters.addParameter() that allowed bypassing maxParameterCount limits. The fix (commit fbd81421629afe8b8a3922d59020cde81caea861 by Apache's Mark Thomas) shipped in upstream release 9.0.74 and is present in 9.0.100. The target code at lines 204-210 of Parameters.java correctly checks `parameterCount >= limit` BEFORE incrementing, preventing the bypass. This is an upstream fix, not a TuxCare backport.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 11.0.0-M2, < 11.0.0-M5; >= 10.1.5, < 10.1.8; >= 9.0.71, < 9.0.74; >= 8.5.85, < 8.5.88), NVD (>= 8.5.85, <= 8.5.87; >= 9.0.71, <= 9.0.73; >= 10.1.5, <= 10.1.7; = 11.0.0-milestone2; = 11.0.0-milestone3; = 11.0.0-milestone4), cve.org (>= 11.0.0-M2, <= 11.0.0-M4; >= 10.1.5, <= 10.1.7; >= 9.0.71, <= 9.0.73; >= 8.5.85, <= 8.5.87), Snyk (>= 8.5.85, < 8.5.88; >= 9.0.71, < 9.0.74; >= 10.1.5, < 10.1.8; >= 11.0.0-M2, < 11.0.0-M5; >= 8.5.85, < 8.5.88; >= 9.0.71, < 9.0.74; >= 10.1.5, < 10.1.8; >= 11.0.0-M2, < 11.0.0-M5; >= 8.5.85, < 8.5.88; >= 9.0.71, < 9.0.74; >= 10.1.5, < 10.1.8; >= 11.0.0-M2, < 11.0.0-M5).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2023-28709"
      },
      "impact_statement": "CVE-2023-28709 is NOT present in Tomcat 9.0.100. The vulnerability was an off-by-one error in Parameters.addParameter() that allowed bypassing maxParameterCount limits. The fix (commit fbd81421629afe8b8a3922d59020cde81caea861 by Apache's Mark Thomas) shipped in upstream release 9.0.74 and is present in 9.0.100. The target code at lines 204-210 of Parameters.java correctly checks `parameterCount >= limit` BEFORE incrementing, preventing the bypass. This is an upstream fix, not a TuxCare backport.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 11.0.0-M2, < 11.0.0-M5; >= 10.1.5, < 10.1.8; >= 9.0.71, < 9.0.74; >= 8.5.85, < 8.5.88), NVD (>= 8.5.85, <= 8.5.87; >= 9.0.71, <= 9.0.73; >= 10.1.5, <= 10.1.7; = 11.0.0-milestone2; = 11.0.0-milestone3; = 11.0.0-milestone4), cve.org (>= 11.0.0-M2, <= 11.0.0-M4; >= 10.1.5, <= 10.1.7; >= 9.0.71, <= 9.0.73; >= 8.5.85, <= 8.5.87), Snyk (>= 8.5.85, < 8.5.88; >= 9.0.71, < 9.0.74; >= 10.1.5, < 10.1.8; >= 11.0.0-M2, < 11.0.0-M5; >= 8.5.85, < 8.5.88; >= 9.0.71, < 9.0.74; >= 10.1.5, < 10.1.8; >= 11.0.0-M2, < 11.0.0-M5; >= 8.5.85, < 8.5.88; >= 9.0.71, < 9.0.74; >= 10.1.5, < 10.1.8; >= 11.0.0-M2, < 11.0.0-M5)."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.100-tuxcare.3",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.100-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-11-04T09:20:30.171913+00:00",
      "status_notes": "Vulnerability CVE-2023-34981 does not affect version 9.0.100-tuxcare.3 of org.apache.tomcat:tomcat-coyote. CVE-2023-34981 is NOT present in Apache Tomcat 9.0.100. The vulnerability was a regression in bug 66512's fix where responses with no HTTP headers would not send the AJP SEND_HEADERS message, causing mod_proxy_ajp to reuse headers from previous requests. The fix (commit 2f0ca23784) was already present in the upstream Apache Tomcat 9.0.100 release before TuxCare onboarded it. The current code uses a `while (needAjpMessageHeader)` loop that ensures SEND_HEADERS is always sent, even when numHeaders == 0, preventing the information leak.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 11.0.0-M5, < 11.0.0-M6; >= 10.1.8, < 10.1.9; >= 9.0.74, < 9.0.75; >= 8.5.88, < 8.5.89), NVD (= 8.5.88; = 9.0.74; = 10.1.8; = 11.0.0-milestone5), cve.org (= 11.0.0-M5; = 10.1.8; = 9.0.74; = 8.5.88; = 10.1.8; = 11.0.0; = 8.5.88; = 9.0.74), Snyk (>= 8.5.88, < 8.5.89; >= 9.0.74, < 9.0.75; >= 10.1.8, < 10.1.9; >= 11.0.0-M5, < 11.0.0-M6; >= 8.5.88, < 8.5.89; >= 9.0.74, < 9.0.75; >= 10.1.8, < 10.1.9; >= 11.0.0-M5, < 11.0.0-M6).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2023-34981"
      },
      "impact_statement": "CVE-2023-34981 is NOT present in Apache Tomcat 9.0.100. The vulnerability was a regression in bug 66512's fix where responses with no HTTP headers would not send the AJP SEND_HEADERS message, causing mod_proxy_ajp to reuse headers from previous requests. The fix (commit 2f0ca23784) was already present in the upstream Apache Tomcat 9.0.100 release before TuxCare onboarded it. The current code uses a `while (needAjpMessageHeader)` loop that ensures SEND_HEADERS is always sent, even when numHeaders == 0, preventing the information leak.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 11.0.0-M5, < 11.0.0-M6; >= 10.1.8, < 10.1.9; >= 9.0.74, < 9.0.75; >= 8.5.88, < 8.5.89), NVD (= 8.5.88; = 9.0.74; = 10.1.8; = 11.0.0-milestone5), cve.org (= 11.0.0-M5; = 10.1.8; = 9.0.74; = 8.5.88; = 10.1.8; = 11.0.0; = 8.5.88; = 9.0.74), Snyk (>= 8.5.88, < 8.5.89; >= 9.0.74, < 9.0.75; >= 10.1.8, < 10.1.9; >= 11.0.0-M5, < 11.0.0-M6; >= 8.5.88, < 8.5.89; >= 9.0.74, < 9.0.75; >= 10.1.8, < 10.1.9; >= 11.0.0-M5, < 11.0.0-M6)."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.100-tuxcare.3",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.100-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-10-28T18:40:55.741562+00:00",
      "status_notes": "Vulnerability CVE-2023-42794 does not affect version 9.0.100-tuxcare.3 of org.apache.tomcat:tomcat-coyote. not_affected \u2014 Target Apache Tomcat 9.0.100 is not affected by CVE-2023-42794. The vulnerability (incomplete cleanup of uploaded files when streams are not closed) was fixed by upstream Apache in version 9.0.81 via commit 43b882b8a5 by Mark Thomas. This fix is present in the target's codebase, shipped in the upstream release 9.0.100. The finalize() method that ensures cleanup of temporary files via garbage co...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2023-42794"
      },
      "impact_statement": "not_affected \u2014 Target Apache Tomcat 9.0.100 is not affected by CVE-2023-42794. The vulnerability (incomplete cleanup of uploaded files when streams are not closed) was fixed by upstream Apache in version 9.0.81 via commit 43b882b8a5 by Mark Thomas. This fix is present in the target's codebase, shipped in the upstream release 9.0.100. The finalize() method that ensures cleanup of temporary files via garbage co..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.100-tuxcare.3",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.100-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-11-03T11:39:32.418284+00:00",
      "status_notes": "Vulnerability CVE-2023-44487 does not affect version 9.0.100-tuxcare.3 of org.apache.tomcat:tomcat-coyote. Apache Tomcat 9.0.100 is not affected by CVE-2023-44487 (HTTP/2 Rapid Reset attack). The upstream Apache Tomcat project fixed this vulnerability in commit 6d1a9fd6642387969e4410b9989c85856b74917a by Mark Thomas on October 5, 2023. This fix was included in the Apache Tomcat 9.0.100 upstream release that TuxCare onboarded. The fix adds overhead tracking for RST_STREAM frames (with a higher weight factor of 50x) and PRIORITY_UPDATE frames, and stops processing when the overhead limit is exceeded, effectively preventing rapid reset attacks.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 11.0.0-M1, < 11.0.0-M12; >= 10.0.0, < 10.1.14; >= 9.0.0, < 9.0.81; >= 8.5.0, < 8.5.94; >= 11.0.0-M1, < 11.0.0-M12; >= 10.0.0, < 10.1.14; >= 9.0.0, < 9.0.81; >= 8.5.0, < 8.5.94), NVD (>= 8.5.0, <= 8.5.93; >= 9.0.0, <= 9.0.80; >= 10.1.0, <= 10.1.13; = 11.0.0-milestone1; = 11.0.0-milestone10; = 11.0.0-milestone11; = 11.0.0-milestone2; = 11.0.0-milestone3; = 11.0.0-milestone4; = 11.0.0-milestone5; = 11.0.0-milestone6; = 11.0.0-milestone7; = 11.0.0-milestone8; = 11.0.0-milestone9), Snyk (< 8.5.94; >= 9.0.0, < 9.0.81; >= 10.0.0, < 10.1.14; >= 11.0.0-M3, < 11.0.0-M12; < 8.5.94; >= 9.0.0, < 9.0.81; >= 10.0.0, < 10.1.14; >= 11.0.0-M3, < 11.0.0-M12).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2023-44487"
      },
      "impact_statement": "Apache Tomcat 9.0.100 is not affected by CVE-2023-44487 (HTTP/2 Rapid Reset attack). The upstream Apache Tomcat project fixed this vulnerability in commit 6d1a9fd6642387969e4410b9989c85856b74917a by Mark Thomas on October 5, 2023. This fix was included in the Apache Tomcat 9.0.100 upstream release that TuxCare onboarded. The fix adds overhead tracking for RST_STREAM frames (with a higher weight factor of 50x) and PRIORITY_UPDATE frames, and stops processing when the overhead limit is exceeded, effectively preventing rapid reset attacks.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 11.0.0-M1, < 11.0.0-M12; >= 10.0.0, < 10.1.14; >= 9.0.0, < 9.0.81; >= 8.5.0, < 8.5.94; >= 11.0.0-M1, < 11.0.0-M12; >= 10.0.0, < 10.1.14; >= 9.0.0, < 9.0.81; >= 8.5.0, < 8.5.94), NVD (>= 8.5.0, <= 8.5.93; >= 9.0.0, <= 9.0.80; >= 10.1.0, <= 10.1.13; = 11.0.0-milestone1; = 11.0.0-milestone10; = 11.0.0-milestone11; = 11.0.0-milestone2; = 11.0.0-milestone3; = 11.0.0-milestone4; = 11.0.0-milestone5; = 11.0.0-milestone6; = 11.0.0-milestone7; = 11.0.0-milestone8; = 11.0.0-milestone9), Snyk (< 8.5.94; >= 9.0.0, < 9.0.81; >= 10.0.0, < 10.1.14; >= 11.0.0-M3, < 11.0.0-M12; < 8.5.94; >= 9.0.0, < 9.0.81; >= 10.0.0, < 10.1.14; >= 11.0.0-M3, < 11.0.0-M12)."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.100-tuxcare.3",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.100-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-10-28T19:07:12.211534+00:00",
      "status_notes": "Vulnerability CVE-2023-45648 does not affect version 9.0.100-tuxcare.3 of org.apache.tomcat:tomcat-coyote. not_affected \u2014 CVE-2023-45648 is not present in Tomcat 9.0.100. The vulnerability (improper parsing of HTTP trailer headers in chunked transfer encoding requests, enabling request smuggling) was fixed in upstream Apache Tomcat through architectural refactoring that introduced the HttpHeaderParser class with proper validation of trailer header names and values. This upstream fix was already present in the 9.0....",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2023-45648"
      },
      "impact_statement": "not_affected \u2014 CVE-2023-45648 is not present in Tomcat 9.0.100. The vulnerability (improper parsing of HTTP trailer headers in chunked transfer encoding requests, enabling request smuggling) was fixed in upstream Apache Tomcat through architectural refactoring that introduced the HttpHeaderParser class with proper validation of trailer header names and values. This upstream fix was already present in the 9.0...."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.100-tuxcare.3",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.100-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-11-03T11:40:00.069704+00:00",
      "status_notes": "Vulnerability CVE-2023-46589 does not affect version 9.0.100-tuxcare.3 of org.apache.tomcat:tomcat-coyote. CVE-2023-46589 is not affecting Apache Tomcat 9.0.100. The vulnerability (improper HTTP trailer header parsing enabling request smuggling) was fixed in the upstream release through a refactoring that introduced HttpHeaderParser with proper validation. The fix validates trailer header names using HttpParser.isToken() and rejects control characters in values using HttpParser.isControl(), matching the CVE-2023-46589 mitigation. This fix was authored by upstream Apache developer Mark Thomas (markt@apache.org) on April 26, 2024 and was already present when TuxCare onboarded version 9.0.100 on December 18, 2025.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 11.0.0-M1, < 11.0.0-M11; >= 10.1.0-M1, < 10.1.16; >= 9.0.0-M1, < 9.0.83; >= 8.5.0, < 8.5.96; >= 11.0.0-M1, < 11.0.0-M11; >= 10.1.0-M1, < 10.1.16; >= 9.0.0-M1, < 9.0.83; >= 8.5.0, < 8.5.96; >= 11.0.0-M1, < 11.0.0-M11), NVD (>= 8.5.0, < 8.5.96; >= 9.0.0, < 9.0.83; >= 10.1.0, < 10.1.16; = 11.0.0-milestone1; = 11.0.0-milestone10; = 11.0.0-milestone2; = 11.0.0-milestone3; = 11.0.0-milestone4; = 11.0.0-milestone5; = 11.0.0-milestone6; = 11.0.0-milestone7; = 11.0.0-milestone8; = 11.0.0-milestone9), cve.org (>= 11.0.0-M1, <= 11.0.0-M10; >= 10.1.0-M1, <= 10.1.15; >= 9.0.0-M1, <= 9.0.82; >= 8.5.0, <= 8.5.95; >= 11.0.0-m1, <= 11.0.0-m10; >= 10.1.0-M1, <= 10.1.15; >= 9.0.0-M1, <= 9.0.82; >= 8.5.0, <= 8.5.95), Snyk (>= 8.5.0, < 8.5.96; >= 9.0.0-M1, < 9.0.83; >= 10.1.0-M1, < 10.1.16; >= 11.0.0-M1, < 11.0.0-M10; >= 8.5.0, < 8.5.96; >= 9.0.0-M1, < 9.0.83; >= 10.1.0-M1, < 10.1.16; >= 11.0.0-M1, < 11.0.0-M10).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2023-46589"
      },
      "impact_statement": "CVE-2023-46589 is not affecting Apache Tomcat 9.0.100. The vulnerability (improper HTTP trailer header parsing enabling request smuggling) was fixed in the upstream release through a refactoring that introduced HttpHeaderParser with proper validation. The fix validates trailer header names using HttpParser.isToken() and rejects control characters in values using HttpParser.isControl(), matching the CVE-2023-46589 mitigation. This fix was authored by upstream Apache developer Mark Thomas (markt@apache.org) on April 26, 2024 and was already present when TuxCare onboarded version 9.0.100 on December 18, 2025.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 11.0.0-M1, < 11.0.0-M11; >= 10.1.0-M1, < 10.1.16; >= 9.0.0-M1, < 9.0.83; >= 8.5.0, < 8.5.96; >= 11.0.0-M1, < 11.0.0-M11; >= 10.1.0-M1, < 10.1.16; >= 9.0.0-M1, < 9.0.83; >= 8.5.0, < 8.5.96; >= 11.0.0-M1, < 11.0.0-M11), NVD (>= 8.5.0, < 8.5.96; >= 9.0.0, < 9.0.83; >= 10.1.0, < 10.1.16; = 11.0.0-milestone1; = 11.0.0-milestone10; = 11.0.0-milestone2; = 11.0.0-milestone3; = 11.0.0-milestone4; = 11.0.0-milestone5; = 11.0.0-milestone6; = 11.0.0-milestone7; = 11.0.0-milestone8; = 11.0.0-milestone9), cve.org (>= 11.0.0-M1, <= 11.0.0-M10; >= 10.1.0-M1, <= 10.1.15; >= 9.0.0-M1, <= 9.0.82; >= 8.5.0, <= 8.5.95; >= 11.0.0-m1, <= 11.0.0-m10; >= 10.1.0-M1, <= 10.1.15; >= 9.0.0-M1, <= 9.0.82; >= 8.5.0, <= 8.5.95), Snyk (>= 8.5.0, < 8.5.96; >= 9.0.0-M1, < 9.0.83; >= 10.1.0-M1, < 10.1.16; >= 11.0.0-M1, < 11.0.0-M10; >= 8.5.0, < 8.5.96; >= 9.0.0-M1, < 9.0.83; >= 10.1.0-M1, < 10.1.16; >= 11.0.0-M1, < 11.0.0-M10)."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.100-tuxcare.3",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.100-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-11-02T18:44:00.098481+00:00",
      "status_notes": "Vulnerability CVE-2024-21733 does not affect version 9.0.100-tuxcare.3 of org.apache.tomcat:tomcat-coyote. not_affected \u2014 Target version 9.0.100 is not affected by CVE-2024-21733. The vulnerability affects Tomcat 9.0.0-M11 through 9.0.43, with the fix available in 9.0.44+. The upstream Apache Tomcat 9.0.100 release already contained the fix (commit d1da266aa1ea541b9f7a356bce9c2cc332658078 by markt@apache.org on 2021-02-25), which was onboarded by TuxCare on 2025-12-18. The target has two IS_IO_ALLOWED checks preve...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2024-21733"
      },
      "impact_statement": "not_affected \u2014 Target version 9.0.100 is not affected by CVE-2024-21733. The vulnerability affects Tomcat 9.0.0-M11 through 9.0.43, with the fix available in 9.0.44+. The upstream Apache Tomcat 9.0.100 release already contained the fix (commit d1da266aa1ea541b9f7a356bce9c2cc332658078 by markt@apache.org on 2021-02-25), which was onboarded by TuxCare on 2025-12-18. The target has two IS_IO_ALLOWED checks preve..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.100-tuxcare.3",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.100-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2024-24549 does not affect version 9.0.100-tuxcare.3 of org.apache.tomcat:tomcat-coyote. CVE-2024-24549 affects Tomcat 9.0.x up to 9.0.82; fixed in 9.0.83+. Target 9.0.100 already contains the fix, so this version is not affected.",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2024-24549"
      },
      "impact_statement": "CVE-2024-24549 affects Tomcat 9.0.x up to 9.0.82; fixed in 9.0.83+. Target 9.0.100 already contains the fix, so this version is not affected."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.100-tuxcare.3",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.100-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-11-03T11:39:32.418284+00:00",
      "status_notes": "Vulnerability CVE-2024-34750 does not affect version 9.0.100-tuxcare.3 of org.apache.tomcat:tomcat-coyote. CVE-2024-34750 is NOT present in Tomcat 9.0.100. The upstream fix commit 9fec9a82887853402833a80b584e3762c7423f5f by Mark Thomas (markt@apache.org) was already present in the Apache Tomcat 9.0.100 release that TuxCare onboarded. The fix adds atomic per-stream protection against double-decrementing the active stream count, preventing the miscounting that led to incorrect infinite timeouts. All defensive mechanisms are in place: the AtomicBoolean removedFromActiveCount flag in Stream.java (line 97), the decrementAndGetActiveRemoteStreamCount() method with compareAndSet protection (lines 949-959), proper increment at stream creation (Http2UpgradeHandler.java line 1632), and the corrected headersEnd validation logic (line 1701). The vulnerable pattern described in the CVE does not exist in this version.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 11.0.0-M1, < 11.0.0-M21; >= 10.1.0-M1, < 10.1.25; >= 9.0.0-M1, < 9.0.90; >= 11.0.0-M1, < 11.0.0-M21; >= 10.1.0-M1, < 10.1.25; >= 9.0.0-M1, < 9.0.90; >= 8.5.0, <= 8.5.100; >= 8.5.0, <= 8.5.100), NVD (>= 9.0.0, < 9.0.90; >= 10.1.0, < 10.1.25; = 11.0.0-milestone1; = 11.0.0-milestone10; = 11.0.0-milestone11; = 11.0.0-milestone12; = 11.0.0-milestone13; = 11.0.0-milestone14; = 11.0.0-milestone15; = 11.0.0-milestone16; = 11.0.0-milestone17; = 11.0.0-milestone18; = 11.0.0-milestone19; = 11.0.0-milestone2; = 11.0.0-milestone20; = 11.0.0-milestone3; = 11.0.0-milestone4; = 11.0.0-milestone5; = 11.0.0-milestone6; = 11.0.0-milestone7; = 11.0.0-milestone8; = 11.0.0-milestone9), cve.org (>= 11.0.0-M1, <= 11.0.0-M20; >= 10.1.0-M1, <= 10.1.24; >= 9.0.0-M1, <= 9.0.89; >= 8.5.0, <= 8.5.100; >= 9.0.0-m1, <= 9.0.89; >= 10.1.0-m1, <= 10.1.24; >= 11.0.0-m1, <= 11.0.0-m20), Snyk (< 9.0.90; >= 10.1.0-M1, < 10.1.25; >= 11.0.0-M1, < 11.0.0-M21; < 9.0.90; >= 10.1.0-M1, < 10.1.25; >= 11.0.0-M1, < 11.0.0-M21).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2024-34750"
      },
      "impact_statement": "CVE-2024-34750 is NOT present in Tomcat 9.0.100. The upstream fix commit 9fec9a82887853402833a80b584e3762c7423f5f by Mark Thomas (markt@apache.org) was already present in the Apache Tomcat 9.0.100 release that TuxCare onboarded. The fix adds atomic per-stream protection against double-decrementing the active stream count, preventing the miscounting that led to incorrect infinite timeouts. All defensive mechanisms are in place: the AtomicBoolean removedFromActiveCount flag in Stream.java (line 97), the decrementAndGetActiveRemoteStreamCount() method with compareAndSet protection (lines 949-959), proper increment at stream creation (Http2UpgradeHandler.java line 1632), and the corrected headersEnd validation logic (line 1701). The vulnerable pattern described in the CVE does not exist in this version.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 11.0.0-M1, < 11.0.0-M21; >= 10.1.0-M1, < 10.1.25; >= 9.0.0-M1, < 9.0.90; >= 11.0.0-M1, < 11.0.0-M21; >= 10.1.0-M1, < 10.1.25; >= 9.0.0-M1, < 9.0.90; >= 8.5.0, <= 8.5.100; >= 8.5.0, <= 8.5.100), NVD (>= 9.0.0, < 9.0.90; >= 10.1.0, < 10.1.25; = 11.0.0-milestone1; = 11.0.0-milestone10; = 11.0.0-milestone11; = 11.0.0-milestone12; = 11.0.0-milestone13; = 11.0.0-milestone14; = 11.0.0-milestone15; = 11.0.0-milestone16; = 11.0.0-milestone17; = 11.0.0-milestone18; = 11.0.0-milestone19; = 11.0.0-milestone2; = 11.0.0-milestone20; = 11.0.0-milestone3; = 11.0.0-milestone4; = 11.0.0-milestone5; = 11.0.0-milestone6; = 11.0.0-milestone7; = 11.0.0-milestone8; = 11.0.0-milestone9), cve.org (>= 11.0.0-M1, <= 11.0.0-M20; >= 10.1.0-M1, <= 10.1.24; >= 9.0.0-M1, <= 9.0.89; >= 8.5.0, <= 8.5.100; >= 9.0.0-m1, <= 9.0.89; >= 10.1.0-m1, <= 10.1.24; >= 11.0.0-m1, <= 11.0.0-m20), Snyk (< 9.0.90; >= 10.1.0-M1, < 10.1.25; >= 11.0.0-M1, < 11.0.0-M21; < 9.0.90; >= 10.1.0-M1, < 10.1.25; >= 11.0.0-M1, < 11.0.0-M21)."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.100-tuxcare.3",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.100-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-11-03T11:39:32.418284+00:00",
      "status_notes": "Vulnerability CVE-2024-38286 does not affect version 9.0.100-tuxcare.3 of org.apache.tomcat:tomcat-coyote. CVE-2024-38286 (TLS handshake re-keying OOM vulnerability) is NOT present in Tomcat 9.0.100. The upstream Apache fix (commit 76c5cce6f0 by Mark Thomas) was already included in the Apache Tomcat 9.0.90 release and all subsequent versions including 9.0.100. The fix adds queue length limits (cap at 100 for NIO2, pending-wrap detection for NIO) to prevent unbounded accumulation of handshake wrap operations during TLS 1.3 client-initiated re-keying. The target contains the complete fix: SecureNio2Channel.java implements handshakeWrapQueueLength counter with HANDSHAKE_WRAP_QUEUE_LENGTH_LIMIT=100; SecureNioChannel.java implements needHandshakeWrap flag; both reset on wrap() and throw exceptions on overflow. This is an upstream fix, not a TuxCare backport.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 11.0.0-M1, < 11.0.0-M21; >= 10.1.0-M1, < 10.1.25; >= 9.0.13, < 9.0.90; >= 8.5.35, <= 8.5.100; >= 7.0.92, <= 7.0.109; >= 11.0.0-M1, < 11.0.0-M21; >= 10.1.0-M1, < 10.1.25; >= 9.0.13, < 9.0.90; >= 8.5.35, <= 8.5.100; >= 7.0.92, <= 7.0.109), NVD (>= 9.0.13, < 9.0.90; >= 10.1.1, < 10.1.25; = 10.1.0-milestone1; = 10.1.0-milestone10; = 10.1.0-milestone11; = 10.1.0-milestone12; = 10.1.0-milestone13; = 10.1.0-milestone14; = 10.1.0-milestone15; = 10.1.0-milestone16; = 10.1.0-milestone17; = 10.1.0-milestone18; = 10.1.0-milestone19; = 10.1.0-milestone2; = 10.1.0-milestone20; = 10.1.0-milestone3; = 10.1.0-milestone4; = 10.1.0-milestone5; = 10.1.0-milestone6; = 10.1.0-milestone7; = 10.1.0-milestone8; = 10.1.0-milestone9; = 11.0.0-milestone1; = 11.0.0-milestone10; = 11.0.0-milestone11; = 11.0.0-milestone12; = 11.0.0-milestone13; = 11.0.0-milestone14; = 11.0.0-milestone15; = 11.0.0-milestone16; = 11.0.0-milestone17; = 11.0.0-milestone18; = 11.0.0-milestone19; = 11.0.0-milestone2; = 11.0.0-milestone20; = 11.0.0-milestone3; = 11.0.0-milestone4; = 11.0.0-milestone5; = 11.0.0-milestone6; = 11.0.0-milestone7; = 11.0.0-milestone8; = 11.0.0-milestone9), cve.org (>= 11.0.0-M1, <= 11.0.0-M20; >= 10.1.0-M1, <= 10.1.24; >= 9.0.13, <= 9.0.89; >= 8.5.35, <= 8.5.100; >= 7.0.92, <= 7.0.109; >= 11.0.0-m1, <= 11.0.0-m20; >= 10.1.0-m1, <= 10.1.24; >= 9.0.13, <= 9.0.89), Snyk (>= 9.0.13, < 9.0.90; >= 10.1.0-M1, < 10.1.25; >= 11.0.0-M1, < 11.0.0-M21; >= 9.0.13, < 9.0.90; >= 10.1.0-M1, < 10.1.25; >= 11.0.0-M1, < 11.0.0-M21).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2024-38286"
      },
      "impact_statement": "CVE-2024-38286 (TLS handshake re-keying OOM vulnerability) is NOT present in Tomcat 9.0.100. The upstream Apache fix (commit 76c5cce6f0 by Mark Thomas) was already included in the Apache Tomcat 9.0.90 release and all subsequent versions including 9.0.100. The fix adds queue length limits (cap at 100 for NIO2, pending-wrap detection for NIO) to prevent unbounded accumulation of handshake wrap operations during TLS 1.3 client-initiated re-keying. The target contains the complete fix: SecureNio2Channel.java implements handshakeWrapQueueLength counter with HANDSHAKE_WRAP_QUEUE_LENGTH_LIMIT=100; SecureNioChannel.java implements needHandshakeWrap flag; both reset on wrap() and throw exceptions on overflow. This is an upstream fix, not a TuxCare backport.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 11.0.0-M1, < 11.0.0-M21; >= 10.1.0-M1, < 10.1.25; >= 9.0.13, < 9.0.90; >= 8.5.35, <= 8.5.100; >= 7.0.92, <= 7.0.109; >= 11.0.0-M1, < 11.0.0-M21; >= 10.1.0-M1, < 10.1.25; >= 9.0.13, < 9.0.90; >= 8.5.35, <= 8.5.100; >= 7.0.92, <= 7.0.109), NVD (>= 9.0.13, < 9.0.90; >= 10.1.1, < 10.1.25; = 10.1.0-milestone1; = 10.1.0-milestone10; = 10.1.0-milestone11; = 10.1.0-milestone12; = 10.1.0-milestone13; = 10.1.0-milestone14; = 10.1.0-milestone15; = 10.1.0-milestone16; = 10.1.0-milestone17; = 10.1.0-milestone18; = 10.1.0-milestone19; = 10.1.0-milestone2; = 10.1.0-milestone20; = 10.1.0-milestone3; = 10.1.0-milestone4; = 10.1.0-milestone5; = 10.1.0-milestone6; = 10.1.0-milestone7; = 10.1.0-milestone8; = 10.1.0-milestone9; = 11.0.0-milestone1; = 11.0.0-milestone10; = 11.0.0-milestone11; = 11.0.0-milestone12; = 11.0.0-milestone13; = 11.0.0-milestone14; = 11.0.0-milestone15; = 11.0.0-milestone16; = 11.0.0-milestone17; = 11.0.0-milestone18; = 11.0.0-milestone19; = 11.0.0-milestone2; = 11.0.0-milestone20; = 11.0.0-milestone3; = 11.0.0-milestone4; = 11.0.0-milestone5; = 11.0.0-milestone6; = 11.0.0-milestone7; = 11.0.0-milestone8; = 11.0.0-milestone9), cve.org (>= 11.0.0-M1, <= 11.0.0-M20; >= 10.1.0-M1, <= 10.1.24; >= 9.0.13, <= 9.0.89; >= 8.5.35, <= 8.5.100; >= 7.0.92, <= 7.0.109; >= 11.0.0-m1, <= 11.0.0-m20; >= 10.1.0-m1, <= 10.1.24; >= 9.0.13, <= 9.0.89), Snyk (>= 9.0.13, < 9.0.90; >= 10.1.0-M1, < 10.1.25; >= 11.0.0-M1, < 11.0.0-M21; >= 9.0.13, < 9.0.90; >= 10.1.0-M1, < 10.1.25; >= 11.0.0-M1, < 11.0.0-M21)."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.100-tuxcare.3",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.100-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-11-03T16:34:22.136729+00:00",
      "status_notes": "Vulnerability CVE-2024-52317 does not affect version 9.0.100-tuxcare.3 of org.apache.tomcat:tomcat-coyote. not_affected \u2014 CVE-2024-52317 does not affect this version. The vulnerability involves incorrect recycling of HTTP/2 request/response objects that could lead to data mix-up between users. The fix (commit 47307ee27a) splits Stream.recycle() into replace() and recycle() methods with double-checked locking to ensure request/response objects are recycled exactly once. This upstream fix was already present in Apac...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2024-52317"
      },
      "impact_statement": "not_affected \u2014 CVE-2024-52317 does not affect this version. The vulnerability involves incorrect recycling of HTTP/2 request/response objects that could lead to data mix-up between users. The fix (commit 47307ee27a) splits Stream.recycle() into replace() and recycle() methods with double-checked locking to ensure request/response objects are recycled exactly once. This upstream fix was already present in Apac..."
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.100-tuxcare.3",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.100-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2025-31650 is fixed in version 9.0.100-tuxcare.3 of org.apache.tomcat:tomcat-coyote.",
      "vulnerability": {
        "name": "CVE-2025-31650"
      }
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.100-tuxcare.3",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.100-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2025-48989 is fixed in version 9.0.100-tuxcare.3 of org.apache.tomcat:tomcat-coyote.",
      "vulnerability": {
        "name": "CVE-2025-48989"
      }
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.100-tuxcare.3",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.100-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2025-52434 is fixed in version 9.0.100-tuxcare.3 of org.apache.tomcat:tomcat-coyote.",
      "vulnerability": {
        "name": "CVE-2025-52434"
      }
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.100-tuxcare.3",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.100-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2025-53506 is fixed in version 9.0.100-tuxcare.3 of org.apache.tomcat:tomcat-coyote.",
      "vulnerability": {
        "name": "CVE-2025-53506"
      }
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.100-tuxcare.3",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.100-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2025-66614 affects version 9.0.100-tuxcare.3 of org.apache.tomcat:tomcat-coyote, and is fixed in 9.0.100-tuxcare.6.",
      "vulnerability": {
        "name": "CVE-2025-66614"
      },
      "action_statement": "Vulnerability CVE-2025-66614 affects version 9.0.100-tuxcare.3 of org.apache.tomcat:tomcat-coyote, and is fixed in 9.0.100-tuxcare.6."
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.100-tuxcare.3",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.100-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2026-24733 is fixed in version 9.0.100-tuxcare.3 of org.apache.tomcat:tomcat-coyote.",
      "vulnerability": {
        "name": "CVE-2026-24733"
      }
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.100-tuxcare.3",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.100-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2026-24734 affects version 9.0.100-tuxcare.3 of org.apache.tomcat:tomcat-coyote.",
      "vulnerability": {
        "name": "CVE-2026-24734"
      },
      "action_statement": "Vulnerability CVE-2026-24734 affects version 9.0.100-tuxcare.3 of org.apache.tomcat:tomcat-coyote."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.100-tuxcare.3",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.100-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2026-24880 affects version 9.0.100-tuxcare.3 of org.apache.tomcat:tomcat-coyote, and is fixed in 9.0.100-tuxcare.6.",
      "vulnerability": {
        "name": "CVE-2026-24880"
      },
      "action_statement": "Vulnerability CVE-2026-24880 affects version 9.0.100-tuxcare.3 of org.apache.tomcat:tomcat-coyote, and is fixed in 9.0.100-tuxcare.6."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.100-tuxcare.3",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.100-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-11-03T16:32:27.596761+00:00",
      "status_notes": "Vulnerability CVE-2026-29129 does not affect version 9.0.100-tuxcare.3 of org.apache.tomcat:tomcat-coyote. not_affected \u2014 Target version 9.0.100 is NOT AFFECTED by CVE-2026-29129. The vulnerability was introduced in upstream Tomcat on 2026-01-06 (commit 4ee45c5571) when TLS 1.3 cipher suite dual-list configuration support was added using HashSet, which loses insertion order. The bug was fixed on 2026-02-20 (commit 8d69b33764) by changing to LinkedHashSet. Version 9.0.100 predates this feature entirely - it never h...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2026-29129"
      },
      "impact_statement": "not_affected \u2014 Target version 9.0.100 is NOT AFFECTED by CVE-2026-29129. The vulnerability was introduced in upstream Tomcat on 2026-01-06 (commit 4ee45c5571) when TLS 1.3 cipher suite dual-list configuration support was added using HashSet, which loses insertion order. The bug was fixed on 2026-02-20 (commit 8d69b33764) by changing to LinkedHashSet. Version 9.0.100 predates this feature entirely - it never h..."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.100-tuxcare.3",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.100-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2026-32990 affects version 9.0.100-tuxcare.3 of org.apache.tomcat:tomcat-coyote.",
      "vulnerability": {
        "name": "CVE-2026-32990"
      },
      "action_statement": "Vulnerability CVE-2026-32990 affects version 9.0.100-tuxcare.3 of org.apache.tomcat:tomcat-coyote."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.100-tuxcare.3",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.100-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2026-41293 affects version 9.0.100-tuxcare.3 of org.apache.tomcat:tomcat-coyote.",
      "vulnerability": {
        "name": "CVE-2026-41293"
      },
      "action_statement": "Vulnerability CVE-2026-41293 affects version 9.0.100-tuxcare.3 of org.apache.tomcat:tomcat-coyote."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.100-tuxcare.3",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.100-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-10-29T00:29:56.875680+00:00",
      "status_notes": "Vulnerability CVE-2026-65637 affects version 9.0.100-tuxcare.3 of org.apache.tomcat:tomcat-coyote.",
      "vulnerability": {
        "name": "CVE-2026-65637"
      },
      "action_statement": "Vulnerability CVE-2026-65637 affects version 9.0.100-tuxcare.3 of org.apache.tomcat:tomcat-coyote."
    }
  ]
}
