{
  "@id": "urn:uuid:e69609a0-a808-41ac-b199-dd9185ccae34",
  "role": "Document Creator",
  "author": "https://tuxcare.com",
  "version": 47,
  "@context": "https://openvex.dev/ns/v0.2.0",
  "timestamp": "2026-11-06T18:34:59.823039+00:00",
  "statements": [
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.90-tuxcare.6",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.90-tuxcare.6"
          }
        }
      ],
      "timestamp": "2026-11-03T16:06:30.945793+00:00",
      "status_notes": "Vulnerability CVE-2014-0095 does not affect version 9.0.90-tuxcare.6 of org.apache.tomcat:tomcat-coyote. not_affected \u2014 CVE-2014-0095 affects Apache Tomcat 8.x before 8.0.4 and was fixed upstream in March 2014 by commit 8884dae60a. The target version (Tomcat 9.0.90) contains this fix in AjpProcessor.java lines 615-617, which handles Content-Length: 0 by immediately setting endOfStream=true and returning false, preventing the thread hang described in the CVE. The fix was already present in the upstream Apache Tom...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2014-0095"
      },
      "impact_statement": "not_affected \u2014 CVE-2014-0095 affects Apache Tomcat 8.x before 8.0.4 and was fixed upstream in March 2014 by commit 8884dae60a. The target version (Tomcat 9.0.90) contains this fix in AjpProcessor.java lines 615-617, which handles Content-Length: 0 by immediately setting endOfStream=true and returning false, preventing the thread hang described in the CVE. The fix was already present in the upstream Apache Tom..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.90-tuxcare.6",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.90-tuxcare.6"
          }
        }
      ],
      "timestamp": "2026-11-06T18:34:59.823039+00:00",
      "status_notes": "Vulnerability CVE-2016-6816 does not affect version 9.0.90-tuxcare.6 of org.apache.tomcat:tomcat-coyote. Prechecker: The upstream fix is already in this version's source history (commit 516bda67). The upstream fix was released in 9.0.0.M12, and version 9.0.90 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": "Prechecker: The upstream fix is already in this version's source history (commit 516bda67). The upstream fix was released in 9.0.0.M12, and version 9.0.90 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.90-tuxcare.6",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.90-tuxcare.6"
          }
        }
      ],
      "timestamp": "2026-11-04T09:20:30.171913+00:00",
      "status_notes": "Vulnerability CVE-2017-5651 does not affect version 9.0.90-tuxcare.6 of org.apache.tomcat:tomcat-coyote. CVE-2017-5651 is NOT present in Apache Tomcat 9.0.90-tuxcare.8. The vulnerability was fixed in upstream commit 9233d9d6a0 (authored by Mark Thomas) which shipped in the upstream release 9.0.90 that TuxCare onboarded. The fix introduces SendfileState tracking to prevent Processors from being cached prematurely when sendfile processing completes quickly, eliminating the response mix-up issue. All fix components are verified present in the target code.\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 is NOT present in Apache Tomcat 9.0.90-tuxcare.8. The vulnerability was fixed in upstream commit 9233d9d6a0 (authored by Mark Thomas) which shipped in the upstream release 9.0.90 that TuxCare onboarded. The fix introduces SendfileState tracking to prevent Processors from being cached prematurely when sendfile processing completes quickly, eliminating the response mix-up issue. All fix components are verified present in the target code.\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.90-tuxcare.6",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.90-tuxcare.6"
          }
        }
      ],
      "timestamp": "2026-11-04T09:15:51.446651+00:00",
      "status_notes": "Vulnerability CVE-2019-0199 does not affect version 9.0.90-tuxcare.6 of org.apache.tomcat:tomcat-coyote. CVE-2019-0199 affected Apache Tomcat 9.0.0.M1 to 9.0.14 due to unbounded blocking I/O on HTTP/2 streams and unlimited acceptance of overhead frames (SETTINGS, PING, PRIORITY), leading to thread exhaustion DoS. The target version 9.0.90 is NOT AFFECTED because upstream vendor (Apache) fixed both vulnerabilities in 9.0.15 (released February 2019): (1) added stream-level read/write timeouts (default 20s) that throw CloseNowException on timeout to release threads; (2) added overhead frame counting that closes connections when overhead frames exceed productive frames. Both fixes were authored by Mark Thomas (markt@apache.org) and were already present in the upstream 9.0.90 release (June 2024) that TuxCare onboarded. The vulnerable code pattern no longer exists in this version.\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 affected Apache Tomcat 9.0.0.M1 to 9.0.14 due to unbounded blocking I/O on HTTP/2 streams and unlimited acceptance of overhead frames (SETTINGS, PING, PRIORITY), leading to thread exhaustion DoS. The target version 9.0.90 is NOT AFFECTED because upstream vendor (Apache) fixed both vulnerabilities in 9.0.15 (released February 2019): (1) added stream-level read/write timeouts (default 20s) that throw CloseNowException on timeout to release threads; (2) added overhead frame counting that closes connections when overhead frames exceed productive frames. Both fixes were authored by Mark Thomas (markt@apache.org) and were already present in the upstream 9.0.90 release (June 2024) that TuxCare onboarded. The vulnerable code pattern no longer exists in this version.\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.90-tuxcare.6",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.90-tuxcare.6"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2020-13934 does not affect version 9.0.90-tuxcare.6 of org.apache.tomcat:tomcat-coyote. CVE-2020-13934 affects Apache Tomcat 9.0.0.M5-9.0.36",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2020-13934"
      },
      "impact_statement": "CVE-2020-13934 affects Apache Tomcat 9.0.0.M5-9.0.36"
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.90-tuxcare.6",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.90-tuxcare.6"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2020-13943 does not affect version 9.0.90-tuxcare.6 of org.apache.tomcat:tomcat-coyote. Fix for CVE-202-13943 for this version has been already backported by the original developers, so brunch 9.0.90 is not vulnerable",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2020-13943"
      },
      "impact_statement": "Fix for CVE-202-13943 for this version has been already backported by the original developers, so brunch 9.0.90 is not vulnerable"
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.90-tuxcare.6",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.90-tuxcare.6"
          }
        }
      ],
      "timestamp": "2026-11-04T09:17:29.431970+00:00",
      "status_notes": "Vulnerability CVE-2020-17527 does not affect version 9.0.90-tuxcare.6 of org.apache.tomcat:tomcat-coyote. Target Tomcat 9.0.90 is NOT affected by CVE-2020-17527. All three fixes for bug 64830 (HpackDecoder shared StringBuilder, ConnectionSettingsBase EnumMap, AbstractProtocol unRead timing) are present in the codebase. These fixes were already included in the upstream Apache Tomcat 9.0.90 release (tag 65977c7d, authored by markt@apache.org) before TuxCare onboarded this version (first TuxCare commit bc69a880). The vulnerable pattern - shared mutable state allowing cross-stream header data leakage in HTTP/2 processing - does not exist in the target.\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": "Target Tomcat 9.0.90 is NOT affected by CVE-2020-17527. All three fixes for bug 64830 (HpackDecoder shared StringBuilder, ConnectionSettingsBase EnumMap, AbstractProtocol unRead timing) are present in the codebase. These fixes were already included in the upstream Apache Tomcat 9.0.90 release (tag 65977c7d, authored by markt@apache.org) before TuxCare onboarded this version (first TuxCare commit bc69a880). The vulnerable pattern - shared mutable state allowing cross-stream header data leakage in HTTP/2 processing - does not exist in the target.\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.90-tuxcare.6",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.90-tuxcare.6"
          }
        }
      ],
      "timestamp": "2026-11-04T09:18:58.233822+00:00",
      "status_notes": "Vulnerability CVE-2021-25122 does not affect version 9.0.90-tuxcare.6 of org.apache.tomcat:tomcat-coyote. Target Tomcat 9.0.90 is not affected by CVE-2021-25122. All three upstream fixes for the h2c request duplication vulnerability are present in the target code. The vulnerability (BZ 64830) involved shared mutable state in HTTP/2 processing that could cause request headers and body data from one user to leak into another user's request. The fixes were authored by Apache committer Mark Thomas and shipped in upstream Tomcat 9.0.90 before TuxCare's onboarding. The target version (9.0.90) is also above the CVE's stated affected range (9.0.0.M1 to 9.0.41).\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": "Target Tomcat 9.0.90 is not affected by CVE-2021-25122. All three upstream fixes for the h2c request duplication vulnerability are present in the target code. The vulnerability (BZ 64830) involved shared mutable state in HTTP/2 processing that could cause request headers and body data from one user to leak into another user's request. The fixes were authored by Apache committer Mark Thomas and shipped in upstream Tomcat 9.0.90 before TuxCare's onboarding. The target version (9.0.90) is also above the CVE's stated affected range (9.0.0.M1 to 9.0.41).\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.90-tuxcare.6",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.90-tuxcare.6"
          }
        }
      ],
      "timestamp": "2026-11-03T11:42:00.511362+00:00",
      "status_notes": "Vulnerability CVE-2022-42252 does not affect version 9.0.90-tuxcare.6 of org.apache.tomcat:tomcat-coyote. The target Tomcat 9.0.90 is NOT vulnerable to CVE-2022-42252. The fix for this request smuggling vulnerability was already present in the upstream Apache Tomcat 9.0.90 release that TuxCare onboarded. The upstream commit 4c7f4fd09d2cc1692112ef70b8ee23a7a037ae77 by Mark Thomas (markt@apache.org) implemented the required defense: malformed Content-Length headers are now always rejected with a 400 response, even when rejectIllegalHeader is set to false. This enforcement of RFC 9112 section 6.3 bullet 5 prevents request smuggling attacks when Tomcat is behind a reverse proxy.\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": "The target Tomcat 9.0.90 is NOT vulnerable to CVE-2022-42252. The fix for this request smuggling vulnerability was already present in the upstream Apache Tomcat 9.0.90 release that TuxCare onboarded. The upstream commit 4c7f4fd09d2cc1692112ef70b8ee23a7a037ae77 by Mark Thomas (markt@apache.org) implemented the required defense: malformed Content-Length headers are now always rejected with a 400 response, even when rejectIllegalHeader is set to false. This enforcement of RFC 9112 section 6.3 bullet 5 prevents request smuggling attacks when Tomcat is behind a reverse proxy.\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.90-tuxcare.6",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.90-tuxcare.6"
          }
        }
      ],
      "timestamp": "2026-11-03T11:41:21.668205+00:00",
      "status_notes": "Vulnerability CVE-2023-24998 does not affect version 9.0.90-tuxcare.6 of org.apache.tomcat:tomcat-coyote. Target is not affected by CVE-2023-24998. The vulnerability (unlimited multipart part processing leading to DoS) is not present because the fix was already included in the upstream Apache Tomcat 9.0.90 release. The defense (fileCountMax counter check in FileUploadBase.parseRequest) is present at lines 281-284, properly integrated in Request.parseParts at line 2635, and active by default with a limit of 10 parts (maxPartCount=10). Fix commit cf77cc545 was authored by Mark Thomas (markt@apache.org) on 2022-12-13, before TuxCare setup on 2025-11-03.\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": "Target is not affected by CVE-2023-24998. The vulnerability (unlimited multipart part processing leading to DoS) is not present because the fix was already included in the upstream Apache Tomcat 9.0.90 release. The defense (fileCountMax counter check in FileUploadBase.parseRequest) is present at lines 281-284, properly integrated in Request.parseParts at line 2635, and active by default with a limit of 10 parts (maxPartCount=10). Fix commit cf77cc545 was authored by Mark Thomas (markt@apache.org) on 2022-12-13, before TuxCare setup on 2025-11-03.\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.90-tuxcare.6",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.90-tuxcare.6"
          }
        }
      ],
      "timestamp": "2026-11-04T09:18:58.233822+00:00",
      "status_notes": "Vulnerability CVE-2023-28709 does not affect version 9.0.90-tuxcare.6 of org.apache.tomcat:tomcat-coyote. CVE-2023-28709 is NOT present in Tomcat 9.0.90. The vulnerability involved an off-by-one error in parameter counting logic where incrementing occurred before limit checking and used the wrong comparison operator (> instead of >=), allowing exactly maxParameterCount query parameters to bypass the limit for multipart uploads. The fix (commit fbd81421629) was authored by Apache developer Mark Thomas on April 11, 2023 and was included in the upstream Apache Tomcat 9.0.90 release (June 14, 2024), over a year before TuxCare onboarded this version. The target code at java/org/apache/tomcat/util/http/Parameters.java:204-210 contains the correct fixed pattern: check `parameterCount >= limit` before incrementing.\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.90. The vulnerability involved an off-by-one error in parameter counting logic where incrementing occurred before limit checking and used the wrong comparison operator (> instead of >=), allowing exactly maxParameterCount query parameters to bypass the limit for multipart uploads. The fix (commit fbd81421629) was authored by Apache developer Mark Thomas on April 11, 2023 and was included in the upstream Apache Tomcat 9.0.90 release (June 14, 2024), over a year before TuxCare onboarded this version. The target code at java/org/apache/tomcat/util/http/Parameters.java:204-210 contains the correct fixed pattern: check `parameterCount >= limit` before incrementing.\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.90-tuxcare.6",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.90-tuxcare.6"
          }
        }
      ],
      "timestamp": "2026-11-04T09:20:30.171913+00:00",
      "status_notes": "Vulnerability CVE-2023-34981 does not affect version 9.0.90-tuxcare.6 of org.apache.tomcat:tomcat-coyote. Apache Tomcat 9.0.90 is not affected by CVE-2023-34981. The vulnerability was a regression in bug 66512's fix that caused AJP responses with no HTTP headers to skip sending the SEND_HEADERS message, leading to header reuse from previous requests. The upstream fix (bug 66591) was committed by Mark Thomas on 2023-05-03 and shipped in Apache Tomcat 9.0.75. The target version 9.0.90 includes this fix as part of its base release, predating all TuxCare modifications. The vulnerable pattern (conditional SEND_HEADERS only when numHeaders > 0) has been replaced with an unconditional while-loop structure that ensures SEND_HEADERS is sent even for empty header sets.\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": "Apache Tomcat 9.0.90 is not affected by CVE-2023-34981. The vulnerability was a regression in bug 66512's fix that caused AJP responses with no HTTP headers to skip sending the SEND_HEADERS message, leading to header reuse from previous requests. The upstream fix (bug 66591) was committed by Mark Thomas on 2023-05-03 and shipped in Apache Tomcat 9.0.75. The target version 9.0.90 includes this fix as part of its base release, predating all TuxCare modifications. The vulnerable pattern (conditional SEND_HEADERS only when numHeaders > 0) has been replaced with an unconditional while-loop structure that ensures SEND_HEADERS is sent even for empty header sets.\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.90-tuxcare.6",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.90-tuxcare.6"
          }
        }
      ],
      "timestamp": "2026-10-28T18:40:55.741562+00:00",
      "status_notes": "Vulnerability CVE-2023-42794 does not affect version 9.0.90-tuxcare.6 of org.apache.tomcat:tomcat-coyote. not_affected \u2014 CVE-2023-42794 affects Tomcat 9.0.70-9.0.80 and 8.5.85-8.5.93. The target is version 9.0.90, which already contains the upstream fix. The vulnerability involved missing automatic cleanup of temporary upload files when application code failed to close file streams, potentially leading to disk exhaustion DoS. The fix adds a finalize() method to DiskFileItem that deletes temporary files during gar...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2023-42794"
      },
      "impact_statement": "not_affected \u2014 CVE-2023-42794 affects Tomcat 9.0.70-9.0.80 and 8.5.85-8.5.93. The target is version 9.0.90, which already contains the upstream fix. The vulnerability involved missing automatic cleanup of temporary upload files when application code failed to close file streams, potentially leading to disk exhaustion DoS. The fix adds a finalize() method to DiskFileItem that deletes temporary files during gar..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.90-tuxcare.6",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.90-tuxcare.6"
          }
        }
      ],
      "timestamp": "2026-11-03T11:39:32.418284+00:00",
      "status_notes": "Vulnerability CVE-2023-44487 does not affect version 9.0.90-tuxcare.6 of org.apache.tomcat:tomcat-coyote. The target Apache Tomcat 9.0.90 is NOT AFFECTED by CVE-2023-44487 (HTTP/2 Rapid Reset attack). The fix was already present in the upstream Apache Tomcat 9.0.90 release that TuxCare onboarded. The defense mechanism tracks RST_STREAM frames with an overhead counter (overheadResetFactor=50, default enabled) and terminates connections exceeding the threshold with HTTP/2 ENHANCE_YOUR_CALM error, preventing rapid reset DoS attacks. Fix commit 6d1a9fd6642387969e4410b9989c85856b74917a by Apache committer Mark Thomas (markt@apache.org) was shipped in the 9.0.90 release before TuxCare's onboarding commit bc69a880a5da2ac3f2eb00da320bd2847900bc1d.\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": "The target Apache Tomcat 9.0.90 is NOT AFFECTED by CVE-2023-44487 (HTTP/2 Rapid Reset attack). The fix was already present in the upstream Apache Tomcat 9.0.90 release that TuxCare onboarded. The defense mechanism tracks RST_STREAM frames with an overhead counter (overheadResetFactor=50, default enabled) and terminates connections exceeding the threshold with HTTP/2 ENHANCE_YOUR_CALM error, preventing rapid reset DoS attacks. Fix commit 6d1a9fd6642387969e4410b9989c85856b74917a by Apache committer Mark Thomas (markt@apache.org) was shipped in the 9.0.90 release before TuxCare's onboarding commit bc69a880a5da2ac3f2eb00da320bd2847900bc1d.\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.90-tuxcare.6",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.90-tuxcare.6"
          }
        }
      ],
      "timestamp": "2026-10-28T19:07:12.211534+00:00",
      "status_notes": "Vulnerability CVE-2023-45648 does not affect version 9.0.90-tuxcare.6 of org.apache.tomcat:tomcat-coyote. not_affected \u2014 Target version 9.0.90 is NOT AFFECTED by CVE-2023-45648. The vulnerable pattern (lack of trailer header validation) does not exist in this version. The upstream Apache Tomcat 9.0.90 release (May 2024) included an architectural refactoring that introduced HttpHeaderParser - a common header parser with built-in validation that prevents the vulnerability. The required defenses (rejecting non-token...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2023-45648"
      },
      "impact_statement": "not_affected \u2014 Target version 9.0.90 is NOT AFFECTED by CVE-2023-45648. The vulnerable pattern (lack of trailer header validation) does not exist in this version. The upstream Apache Tomcat 9.0.90 release (May 2024) included an architectural refactoring that introduced HttpHeaderParser - a common header parser with built-in validation that prevents the vulnerability. The required defenses (rejecting non-token..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.90-tuxcare.6",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.90-tuxcare.6"
          }
        }
      ],
      "timestamp": "2026-11-03T11:40:00.069704+00:00",
      "status_notes": "Vulnerability CVE-2023-46589 does not affect version 9.0.90-tuxcare.6 of org.apache.tomcat:tomcat-coyote. CVE-2023-46589 is NOT present in Tomcat 9.0.90. The vulnerability required malformed HTTP trailer headers (with invalid characters) to cause request boundary confusion. The upstream Apache Tomcat 9.0.90 release includes HttpHeaderParser (commit e87a432f88, April 2024) which implements the necessary validation: rejecting non-token characters in trailer header names and control characters (except horizontal tab) in trailer header values. This provides equivalent protection to the original CVE-2023-46589 patch, though via a refactored architecture. TuxCare onboarded 9.0.90 with this defense already present.\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 present in Tomcat 9.0.90. The vulnerability required malformed HTTP trailer headers (with invalid characters) to cause request boundary confusion. The upstream Apache Tomcat 9.0.90 release includes HttpHeaderParser (commit e87a432f88, April 2024) which implements the necessary validation: rejecting non-token characters in trailer header names and control characters (except horizontal tab) in trailer header values. This provides equivalent protection to the original CVE-2023-46589 patch, though via a refactored architecture. TuxCare onboarded 9.0.90 with this defense already present.\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.90-tuxcare.6",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.90-tuxcare.6"
          }
        }
      ],
      "timestamp": "2026-11-02T18:41:44.135768+00:00",
      "status_notes": "Vulnerability CVE-2024-21733 does not affect version 9.0.90-tuxcare.6 of org.apache.tomcat:tomcat-coyote. not_affected \u2014 CVE-2024-21733 is not present in Apache Tomcat 9.0.90. The vulnerability affected versions 8.5.7-8.5.63 and 9.0.0-M11-9.0.43, and was fixed in upstream releases 8.5.64 and 9.0.44. The target version 9.0.90 includes the upstream fix (commit d1da266aa1, authored by Mark Thomas on 2021-02-24) which adds IS_IO_ALLOWED checks before attempting error reporting operations that could leak sensitive inf...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2024-21733"
      },
      "impact_statement": "not_affected \u2014 CVE-2024-21733 is not present in Apache Tomcat 9.0.90. The vulnerability affected versions 8.5.7-8.5.63 and 9.0.0-M11-9.0.43, and was fixed in upstream releases 8.5.64 and 9.0.44. The target version 9.0.90 includes the upstream fix (commit d1da266aa1, authored by Mark Thomas on 2021-02-24) which adds IS_IO_ALLOWED checks before attempting error reporting operations that could leak sensitive inf..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.90-tuxcare.6",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.90-tuxcare.6"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2024-24549 does not affect version 9.0.90-tuxcare.6 of org.apache.tomcat:tomcat-coyote. CVE-2024-24549 is NOT present in Apache Tomcat 9.0.90. The vulnerability (delayed HTTP/2 header validation causing DoS) was fixed by upstream Apache in version 9.0.86 via commit 8e03be9f26 (authored by Mark Thomas, markt@apache.org). Version 9.0.90 inherited this fix from the upstream release. Code inspection confirms the fix is fully applied: readHeadersFrame() and readContinuationFrame() both call validateHeaders() immediately after processing each frame, and the delayed validation in onHeadersComplete() has been removed. TuxCare backported this CVE to older versions (9.0.83, 9.0.75, 10.1.18) but no backport was needed for 9.0.90 as it already contained the upstream fix.",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2024-24549"
      },
      "impact_statement": "CVE-2024-24549 is NOT present in Apache Tomcat 9.0.90. The vulnerability (delayed HTTP/2 header validation causing DoS) was fixed by upstream Apache in version 9.0.86 via commit 8e03be9f26 (authored by Mark Thomas, markt@apache.org). Version 9.0.90 inherited this fix from the upstream release. Code inspection confirms the fix is fully applied: readHeadersFrame() and readContinuationFrame() both call validateHeaders() immediately after processing each frame, and the delayed validation in onHeadersComplete() has been removed. TuxCare backported this CVE to older versions (9.0.83, 9.0.75, 10.1.18) but no backport was needed for 9.0.90 as it already contained the upstream fix."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.90-tuxcare.6",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.90-tuxcare.6"
          }
        }
      ],
      "timestamp": "2026-11-03T11:39:32.418284+00:00",
      "status_notes": "Vulnerability CVE-2024-34750 does not affect version 9.0.90-tuxcare.6 of org.apache.tomcat:tomcat-coyote. CVE-2024-34750 is not present in the target. The vulnerability involved miscounting of active HTTP/2 streams during exceptional header processing, leading to incorrect connection timeouts. The fix was authored by Apache Tomcat upstream (Mark Thomas, markt@apache.org) in commit 9fec9a82887853402833a80b584e3762c7423f5f and shipped in the upstream 9.0.90 release. The target repository is based on this upstream release, so the vulnerable pattern is absent. All fix components verified: per-stream atomic flag (removedFromActiveCount), CAS-protected decrement method, corrected stream counting in headersStart/headersEnd.\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 the target. The vulnerability involved miscounting of active HTTP/2 streams during exceptional header processing, leading to incorrect connection timeouts. The fix was authored by Apache Tomcat upstream (Mark Thomas, markt@apache.org) in commit 9fec9a82887853402833a80b584e3762c7423f5f and shipped in the upstream 9.0.90 release. The target repository is based on this upstream release, so the vulnerable pattern is absent. All fix components verified: per-stream atomic flag (removedFromActiveCount), CAS-protected decrement method, corrected stream counting in headersStart/headersEnd.\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.90-tuxcare.6",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.90-tuxcare.6"
          }
        }
      ],
      "timestamp": "2026-11-03T11:39:32.418284+00:00",
      "status_notes": "Vulnerability CVE-2024-38286 does not affect version 9.0.90-tuxcare.6 of org.apache.tomcat:tomcat-coyote. CVE-2024-38286 affects Apache Tomcat versions 9.0.13-9.0.89 due to unbounded queuing of TLS handshake wrap operations causing OutOfMemoryError. The target version 9.0.90 contains the upstream fix (commit 76c5cce6f0b by Mark Thomas) which adds queue-length limits: HANDSHAKE_WRAP_QUEUE_LENGTH_LIMIT=100 for SecureNio2Channel and needHandshakeWrap flag protection for SecureNioChannel. This fix was already present in the upstream Apache Tomcat 9.0.90 release that TuxCare onboarded, so the vulnerable pattern does not exist in the target.\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 affects Apache Tomcat versions 9.0.13-9.0.89 due to unbounded queuing of TLS handshake wrap operations causing OutOfMemoryError. The target version 9.0.90 contains the upstream fix (commit 76c5cce6f0b by Mark Thomas) which adds queue-length limits: HANDSHAKE_WRAP_QUEUE_LENGTH_LIMIT=100 for SecureNio2Channel and needHandshakeWrap flag protection for SecureNioChannel. This fix was already present in the upstream Apache Tomcat 9.0.90 release that TuxCare onboarded, so the vulnerable pattern does not exist in the target.\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.90-tuxcare.6",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.90-tuxcare.6"
          }
        }
      ],
      "timestamp": "2026-11-03T16:33:25.157477+00:00",
      "status_notes": "Vulnerability CVE-2024-52317 does not affect version 9.0.90-tuxcare.6 of org.apache.tomcat:tomcat-coyote. not_affected \u2014 Target version 9.0.90 is NOT AFFECTED by CVE-2024-52317. The vulnerability requires request/response object recycling and pooling, a mechanism that was introduced in version 9.0.92. In 9.0.90, the Stream.recycle() method only replaces the Stream object with a lighter RecycledStream but never calls coyoteRequest.recycle() or coyoteResponse.recycle(). Each HTTP/2 stream creates new Request/Respon...",
      "justification": "vulnerable_code_not_in_execute_path",
      "vulnerability": {
        "name": "CVE-2024-52317"
      },
      "impact_statement": "not_affected \u2014 Target version 9.0.90 is NOT AFFECTED by CVE-2024-52317. The vulnerability requires request/response object recycling and pooling, a mechanism that was introduced in version 9.0.92. In 9.0.90, the Stream.recycle() method only replaces the Stream object with a lighter RecycledStream but never calls coyoteRequest.recycle() or coyoteResponse.recycle(). Each HTTP/2 stream creates new Request/Respon..."
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.90-tuxcare.6",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.90-tuxcare.6"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2025-31650 is fixed in version 9.0.90-tuxcare.6 of org.apache.tomcat:tomcat-coyote.",
      "vulnerability": {
        "name": "CVE-2025-31650"
      }
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.90-tuxcare.6",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.90-tuxcare.6"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2025-48989 is fixed in version 9.0.90-tuxcare.6 of org.apache.tomcat:tomcat-coyote.",
      "vulnerability": {
        "name": "CVE-2025-48989"
      }
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.90-tuxcare.6",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.90-tuxcare.6"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2025-52434 is fixed in version 9.0.90-tuxcare.6 of org.apache.tomcat:tomcat-coyote.",
      "vulnerability": {
        "name": "CVE-2025-52434"
      }
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.90-tuxcare.6",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.90-tuxcare.6"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2025-53506 is fixed in version 9.0.90-tuxcare.6 of org.apache.tomcat:tomcat-coyote.",
      "vulnerability": {
        "name": "CVE-2025-53506"
      }
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.90-tuxcare.6",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.90-tuxcare.6"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2025-66614 is fixed in version 9.0.90-tuxcare.6 of org.apache.tomcat:tomcat-coyote.",
      "vulnerability": {
        "name": "CVE-2025-66614"
      }
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.90-tuxcare.6",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.90-tuxcare.6"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2026-24733 is fixed in version 9.0.90-tuxcare.6 of org.apache.tomcat:tomcat-coyote.",
      "vulnerability": {
        "name": "CVE-2026-24733"
      }
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.90-tuxcare.6",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.90-tuxcare.6"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2026-24734 affects version 9.0.90-tuxcare.6 of org.apache.tomcat:tomcat-coyote.",
      "vulnerability": {
        "name": "CVE-2026-24734"
      },
      "action_statement": "Vulnerability CVE-2026-24734 affects version 9.0.90-tuxcare.6 of org.apache.tomcat:tomcat-coyote."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.90-tuxcare.6",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.90-tuxcare.6"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2026-24880 affects version 9.0.90-tuxcare.6 of org.apache.tomcat:tomcat-coyote, and is fixed in 9.0.90-tuxcare.7.",
      "vulnerability": {
        "name": "CVE-2026-24880"
      },
      "action_statement": "Vulnerability CVE-2026-24880 affects version 9.0.90-tuxcare.6 of org.apache.tomcat:tomcat-coyote, and is fixed in 9.0.90-tuxcare.7."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.90-tuxcare.6",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.90-tuxcare.6"
          }
        }
      ],
      "timestamp": "2026-11-03T16:28:57.615729+00:00",
      "status_notes": "Vulnerability CVE-2026-29129 does not affect version 9.0.90-tuxcare.6 of org.apache.tomcat:tomcat-coyote. not_affected \u2014 Target version 9.0.90 is NOT affected by CVE-2026-29129. The vulnerability was introduced when TLS 1.3 cipher suite configuration was added in later versions (commit 4ee45c5571), where a HashSet was incorrectly used to combine cipher suites, failing to preserve the configured preference order. The fix (commit 8d69b33764) changed HashSet to LinkedHashSet. Version 9.0.90 predates this feature ent...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2026-29129"
      },
      "impact_statement": "not_affected \u2014 Target version 9.0.90 is NOT affected by CVE-2026-29129. The vulnerability was introduced when TLS 1.3 cipher suite configuration was added in later versions (commit 4ee45c5571), where a HashSet was incorrectly used to combine cipher suites, failing to preserve the configured preference order. The fix (commit 8d69b33764) changed HashSet to LinkedHashSet. Version 9.0.90 predates this feature ent..."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.90-tuxcare.6",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.90-tuxcare.6"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2026-32990 affects version 9.0.90-tuxcare.6 of org.apache.tomcat:tomcat-coyote.",
      "vulnerability": {
        "name": "CVE-2026-32990"
      },
      "action_statement": "Vulnerability CVE-2026-32990 affects version 9.0.90-tuxcare.6 of org.apache.tomcat:tomcat-coyote."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.90-tuxcare.6",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.90-tuxcare.6"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2026-41293 affects version 9.0.90-tuxcare.6 of org.apache.tomcat:tomcat-coyote.",
      "vulnerability": {
        "name": "CVE-2026-41293"
      },
      "action_statement": "Vulnerability CVE-2026-41293 affects version 9.0.90-tuxcare.6 of org.apache.tomcat:tomcat-coyote."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.90-tuxcare.6",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@9.0.90-tuxcare.6"
          }
        }
      ],
      "timestamp": "2026-10-29T00:29:56.875680+00:00",
      "status_notes": "Vulnerability CVE-2026-65637 affects version 9.0.90-tuxcare.6 of org.apache.tomcat:tomcat-coyote.",
      "vulnerability": {
        "name": "CVE-2026-65637"
      },
      "action_statement": "Vulnerability CVE-2026-65637 affects version 9.0.90-tuxcare.6 of org.apache.tomcat:tomcat-coyote."
    }
  ]
}
