{
  "@id": "urn:uuid:f0e8e322-05b3-4b79-8f81-d244184e946f",
  "role": "Document Creator",
  "author": "https://tuxcare.com",
  "version": 48,
  "@context": "https://openvex.dev/ns/v0.2.0",
  "timestamp": "2026-11-06T17:20:00.095414+00:00",
  "statements": [
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.apache.tomcat/tomcat-coyote@8.5.100.tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@8.5.100.tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-11-03T16:05:19.852884+00:00",
      "status_notes": "Vulnerability CVE-2014-0095 does not affect version 8.5.100.tuxcare.2 of org.apache.tomcat:tomcat-coyote. not_affected \u2014 Apache Tomcat 8.5.100 is not affected by CVE-2014-0095. The vulnerability, which caused denial of service through thread consumption when processing AJP requests with Content-Length: 0, was fixed in the upstream release before TuxCare onboarded this version. The fix (commit 1bd7d41498 by Mark Thomas on March 17, 2014) properly handles zero-length content by setting endOfStream=true and returnin...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2014-0095"
      },
      "impact_statement": "not_affected \u2014 Apache Tomcat 8.5.100 is not affected by CVE-2014-0095. The vulnerability, which caused denial of service through thread consumption when processing AJP requests with Content-Length: 0, was fixed in the upstream release before TuxCare onboarded this version. The fix (commit 1bd7d41498 by Mark Thomas on March 17, 2014) properly handles zero-length content by setting endOfStream=true and returnin..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.apache.tomcat/tomcat-coyote@8.5.100.tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@8.5.100.tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2016-6816 does not affect version 8.5.100.tuxcare.2 of org.apache.tomcat:tomcat-coyote. Version 8.5.100 is not vulnerable. Summary: The target repository (Tomcat 8.5.100-tuxcare.10) contains the HTTP request line parsing feature described in CVE-2016-6816, but the vendor's fix has been applied. The fix was released in Tomcat 8.5.7, and the target version is much newer.",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2016-6816"
      },
      "impact_statement": "Version 8.5.100 is not vulnerable. Summary: The target repository (Tomcat 8.5.100-tuxcare.10) contains the HTTP request line parsing feature described in CVE-2016-6816, but the vendor's fix has been applied. The fix was released in Tomcat 8.5.7, and the target version is much newer."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.apache.tomcat/tomcat-coyote@8.5.100.tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@8.5.100.tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2017-5651 does not affect version 8.5.100.tuxcare.2 of org.apache.tomcat:tomcat-coyote. CVE-2017-5651 affects Apache Tomcat 8.5.0-8.5.12",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2017-5651"
      },
      "impact_statement": "CVE-2017-5651 affects Apache Tomcat 8.5.0-8.5.12"
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.apache.tomcat/tomcat-coyote@8.5.100.tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@8.5.100.tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-11-04T09:15:51.446651+00:00",
      "status_notes": "Vulnerability CVE-2019-0199 does not affect version 8.5.100.tuxcare.2 of org.apache.tomcat:tomcat-coyote. CVE-2019-0199 is not present in the target. All three defense mechanisms from the vendor patches are present and actively enforced in the codebase: (1) stream read timeout with 20s default enforced at Stream.java:1263-1280, (2) stream write timeout with 20s default enforced at Stream.java:254-258, (3) overhead frame counting enforced at Http2UpgradeHandler.java:387-391. The fixes were authored by Mark Thomas (markt@apache.org) in February 2019 (commits 2c5939e1, 65f4b6d1, and related) and shipped in Apache Tomcat 8.5.38. Target version 8.5.100 (released January 2024) is based on an upstream release that includes all CVE-2019-0199 fixes. The fix commit is an ancestor of the 8.5.100 tag and predates the first TuxCare commit (0ee1c76d) in this repository's history.\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 is not present in the target. All three defense mechanisms from the vendor patches are present and actively enforced in the codebase: (1) stream read timeout with 20s default enforced at Stream.java:1263-1280, (2) stream write timeout with 20s default enforced at Stream.java:254-258, (3) overhead frame counting enforced at Http2UpgradeHandler.java:387-391. The fixes were authored by Mark Thomas (markt@apache.org) in February 2019 (commits 2c5939e1, 65f4b6d1, and related) and shipped in Apache Tomcat 8.5.38. Target version 8.5.100 (released January 2024) is based on an upstream release that includes all CVE-2019-0199 fixes. The fix commit is an ancestor of the 8.5.100 tag and predates the first TuxCare commit (0ee1c76d) in this repository's history.\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@8.5.100.tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@8.5.100.tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2020-13934 does not affect version 8.5.100.tuxcare.2 of org.apache.tomcat:tomcat-coyote. CVE-2020-13934 affects Apache Tomcat 8.5.1-8.5.56",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2020-13934"
      },
      "impact_statement": "CVE-2020-13934 affects Apache Tomcat 8.5.1-8.5.56"
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.apache.tomcat/tomcat-coyote@8.5.100.tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@8.5.100.tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2020-13943 does not affect version 8.5.100.tuxcare.2 of org.apache.tomcat:tomcat-coyote. Version 8.5.100 is not vulnerable. Summary: The target repository is NOT vulnerable to CVE-2020-13943. The security fix has been applied: the concurrent stream limit check has been correctly moved from headersStart() to headersEnd(), preventing HTTP header leakage between requests. [terminalized not_affected from patch_application_manual/not_vulnerable]",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2020-13943"
      },
      "impact_statement": "Version 8.5.100 is not vulnerable. Summary: The target repository is NOT vulnerable to CVE-2020-13943. The security fix has been applied: the concurrent stream limit check has been correctly moved from headersStart() to headersEnd(), preventing HTTP header leakage between requests. [terminalized not_affected from patch_application_manual/not_vulnerable]"
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.apache.tomcat/tomcat-coyote@8.5.100.tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@8.5.100.tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-11-04T09:17:29.431970+00:00",
      "status_notes": "Vulnerability CVE-2020-17527 does not affect version 8.5.100.tuxcare.2 of org.apache.tomcat:tomcat-coyote. CVE-2020-17527 is not present in Apache Tomcat 8.5.100. The vulnerability affected versions 8.5.0 to 8.5.59, and the fix (BZ 64830) was shipped in upstream Apache Tomcat 8.5.100 on March 19, 2024. The fix removed shared mutable state in HTTP/2 HPACK header processing by converting the instance-level StringBuilder to method-local variables, changing ConnectionSettingsBase maps to ConcurrentHashMap for thread safety, and fixing leftover input handling in AbstractProtocol. TuxCare onboarded version 8.5.100 which already contained these upstream fixes authored by markt@apache.org on November 9, 2020.\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 is not present in Apache Tomcat 8.5.100. The vulnerability affected versions 8.5.0 to 8.5.59, and the fix (BZ 64830) was shipped in upstream Apache Tomcat 8.5.100 on March 19, 2024. The fix removed shared mutable state in HTTP/2 HPACK header processing by converting the instance-level StringBuilder to method-local variables, changing ConnectionSettingsBase maps to ConcurrentHashMap for thread safety, and fixing leftover input handling in AbstractProtocol. TuxCare onboarded version 8.5.100 which already contained these upstream fixes authored by markt@apache.org on November 9, 2020.\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@8.5.100.tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@8.5.100.tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-11-04T09:17:29.431970+00:00",
      "status_notes": "Vulnerability CVE-2021-25122 does not affect version 8.5.100.tuxcare.2 of org.apache.tomcat:tomcat-coyote. Apache Tomcat 8.5.100 is not affected by CVE-2021-25122. All four BZ 64830 fixes addressing h2c request corruption (HPACK decoder concurrency, processor recycling, thread-safe settings maps, leftover input timing) are present in HEAD. The fixes were authored by upstream Apache committer Mark Thomas (markt@apache.org) and shipped in the upstream 8.5.100 release before TuxCare onboarded it. The vulnerable code patterns have been replaced with the fixed versions: HpackDecoder uses local StringBuilder instead of shared instance, ConnectionSettingsBase uses ConcurrentHashMap instead of HashMap/EnumMap, AbstractProtocol properly releases processors before h2c upgrade, and restores leftover input at the correct time.\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": "Apache Tomcat 8.5.100 is not affected by CVE-2021-25122. All four BZ 64830 fixes addressing h2c request corruption (HPACK decoder concurrency, processor recycling, thread-safe settings maps, leftover input timing) are present in HEAD. The fixes were authored by upstream Apache committer Mark Thomas (markt@apache.org) and shipped in the upstream 8.5.100 release before TuxCare onboarded it. The vulnerable code patterns have been replaced with the fixed versions: HpackDecoder uses local StringBuilder instead of shared instance, ConnectionSettingsBase uses ConcurrentHashMap instead of HashMap/EnumMap, AbstractProtocol properly releases processors before h2c upgrade, and restores leftover input at the correct time.\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@8.5.100.tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@8.5.100.tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-11-03T11:42:00.511362+00:00",
      "status_notes": "Vulnerability CVE-2022-42252 does not affect version 8.5.100.tuxcare.2 of org.apache.tomcat:tomcat-coyote. CVE-2022-42252: Target Tomcat 8.5.100 is NOT AFFECTED. The vulnerability (accepting invalid Content-Length headers when rejectIllegalHeader=false, enabling request smuggling) is not present because the upstream fix was already included in the 8.5.100 release. The fix validates Content-Length header syntax and always rejects malformed Content-Length headers with a 400 response, overriding the rejectIllegalHeader configuration. Fix authored by Mark Thomas (Apache upstream) in commit a1c07906d8d, dated 2022-10-03, which predates TuxCare's onboarding of 8.5.100. CVE affected versions: 8.5.0-8.5.82; target is 8.5.100 (above the affected range).\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: Target Tomcat 8.5.100 is NOT AFFECTED. The vulnerability (accepting invalid Content-Length headers when rejectIllegalHeader=false, enabling request smuggling) is not present because the upstream fix was already included in the 8.5.100 release. The fix validates Content-Length header syntax and always rejects malformed Content-Length headers with a 400 response, overriding the rejectIllegalHeader configuration. Fix authored by Mark Thomas (Apache upstream) in commit a1c07906d8d, dated 2022-10-03, which predates TuxCare's onboarding of 8.5.100. CVE affected versions: 8.5.0-8.5.82; target is 8.5.100 (above the affected range).\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@8.5.100.tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@8.5.100.tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-11-03T11:41:21.668205+00:00",
      "status_notes": "Vulnerability CVE-2023-24998 does not affect version 8.5.100.tuxcare.2 of org.apache.tomcat:tomcat-coyote. CVE-2023-24998 (DoS via unlimited file upload parts) is not present in Apache Tomcat 8.5.100. The complete fix was shipped in the upstream Apache release before TuxCare adoption. All defense components are present: the fileCountMax field, getter/setter methods, FileCountLimitExceededException class, the check in FileUploadBase.parseRequest() that throws an exception when items.size() == fileCountMax, and Request.java integration that sets the limit based on connector configuration (maxParameterCount/maxPartCount). The fix was introduced in upstream commit 9ca96c8c1eba86c0aaa2e6be581ba2a7d4d4ae6e by Mark Thomas (markt@apache.org), confirmed as an ancestor of the first TuxCare commit e0a4054d041b17553040c75fe87456e3d37c136a.\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 (DoS via unlimited file upload parts) is not present in Apache Tomcat 8.5.100. The complete fix was shipped in the upstream Apache release before TuxCare adoption. All defense components are present: the fileCountMax field, getter/setter methods, FileCountLimitExceededException class, the check in FileUploadBase.parseRequest() that throws an exception when items.size() == fileCountMax, and Request.java integration that sets the limit based on connector configuration (maxParameterCount/maxPartCount). The fix was introduced in upstream commit 9ca96c8c1eba86c0aaa2e6be581ba2a7d4d4ae6e by Mark Thomas (markt@apache.org), confirmed as an ancestor of the first TuxCare commit e0a4054d041b17553040c75fe87456e3d37c136a.\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@8.5.100.tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@8.5.100.tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-11-04T09:18:58.233822+00:00",
      "status_notes": "Vulnerability CVE-2023-28709 does not affect version 8.5.100.tuxcare.2 of org.apache.tomcat:tomcat-coyote. CVE-2023-28709 is NOT present in Tomcat 8.5.100-tuxcare.10. The vulnerability involved an off-by-one error in parameter counting that allowed bypassing maxParameterCount limits. The fix was already included in the upstream Apache Tomcat 8.5.100 release (commit 5badf94e79e5 by Mark Thomas, 2023-04-11) before TuxCare onboarded this version. The current code correctly checks the limit BEFORE incrementing the counter and uses >= comparison, preventing the bypass.\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 8.5.100-tuxcare.10. The vulnerability involved an off-by-one error in parameter counting that allowed bypassing maxParameterCount limits. The fix was already included in the upstream Apache Tomcat 8.5.100 release (commit 5badf94e79e5 by Mark Thomas, 2023-04-11) before TuxCare onboarded this version. The current code correctly checks the limit BEFORE incrementing the counter and uses >= comparison, preventing the bypass.\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@8.5.100.tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@8.5.100.tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-11-04T09:20:30.171913+00:00",
      "status_notes": "Vulnerability CVE-2023-34981 does not affect version 8.5.100.tuxcare.2 of org.apache.tomcat:tomcat-coyote. The target (Apache Tomcat 8.5.100-tuxcare.10) is NOT affected by CVE-2023-34981. The vulnerability was a regression introduced by the fix for bug 66512 (commit 23e6451af2, March 6, 2023), where responses with no HTTP headers would not send an AJP SEND_HEADERS message, causing mod_proxy_ajp to reuse headers from previous requests. This regression was fixed by upstream in commit 2214c80305 (bug 66591, May 3, 2023), which restructured the code to ensure SEND_HEADERS is always sent even when numHeaders=0. The fix was already present in the upstream release that TuxCare onboarded, making this an upstream-resolved issue.\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": "The target (Apache Tomcat 8.5.100-tuxcare.10) is NOT affected by CVE-2023-34981. The vulnerability was a regression introduced by the fix for bug 66512 (commit 23e6451af2, March 6, 2023), where responses with no HTTP headers would not send an AJP SEND_HEADERS message, causing mod_proxy_ajp to reuse headers from previous requests. This regression was fixed by upstream in commit 2214c80305 (bug 66591, May 3, 2023), which restructured the code to ensure SEND_HEADERS is always sent even when numHeaders=0. The fix was already present in the upstream release that TuxCare onboarded, making this an upstream-resolved issue.\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@8.5.100.tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@8.5.100.tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-10-28T18:40:55.741562+00:00",
      "status_notes": "Vulnerability CVE-2023-42794 does not affect version 8.5.100.tuxcare.2 of org.apache.tomcat:tomcat-coyote. not_affected \u2014 CVE-2023-42794 affects Apache Tomcat 8.5.85-8.5.93 due to missing finalize() cleanup in DiskFileItem, causing temporary uploaded files to persist indefinitely when streams aren't properly closed. The target version 8.5.100 includes the upstream fix (commit c99ffc30e9) that restores the finalize() method to delete temporary files during garbage collection. This fix was authored by Mark Thomas (m...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2023-42794"
      },
      "impact_statement": "not_affected \u2014 CVE-2023-42794 affects Apache Tomcat 8.5.85-8.5.93 due to missing finalize() cleanup in DiskFileItem, causing temporary uploaded files to persist indefinitely when streams aren't properly closed. The target version 8.5.100 includes the upstream fix (commit c99ffc30e9) that restores the finalize() method to delete temporary files during garbage collection. This fix was authored by Mark Thomas (m..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.apache.tomcat/tomcat-coyote@8.5.100.tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@8.5.100.tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-11-03T11:39:32.418284+00:00",
      "status_notes": "Vulnerability CVE-2023-44487 does not affect version 8.5.100.tuxcare.2 of org.apache.tomcat:tomcat-coyote. CVE-2023-44487 (HTTP/2 Rapid Reset) was fixed in upstream Apache Tomcat commit 944332bb15 on Oct 5, 2023 by Mark Thomas. This fix was included in the Tomcat 8.5.100 release (Mar 19, 2024) before TuxCare onboarded the version (May 7, 2025). The target repository contains the complete mitigation: overheadResetFactor (default 50) is applied to RST_STREAM frames, and connections exceeding the overhead limit are closed. The vulnerable pattern is not present because the upstream vendor shipped the fix in this release.\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": "CVE-2023-44487 (HTTP/2 Rapid Reset) was fixed in upstream Apache Tomcat commit 944332bb15 on Oct 5, 2023 by Mark Thomas. This fix was included in the Tomcat 8.5.100 release (Mar 19, 2024) before TuxCare onboarded the version (May 7, 2025). The target repository contains the complete mitigation: overheadResetFactor (default 50) is applied to RST_STREAM frames, and connections exceeding the overhead limit are closed. The vulnerable pattern is not present because the upstream vendor shipped the fix in this release.\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@8.5.100.tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@8.5.100.tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-10-28T19:05:19.418788+00:00",
      "status_notes": "Vulnerability CVE-2023-45648 does not affect version 8.5.100.tuxcare.2 of org.apache.tomcat:tomcat-coyote. not_affected \u2014 Target Apache Tomcat 8.5.100 is NOT vulnerable to CVE-2023-45648. The upstream fix for HTTP trailer header validation was already present in the Apache Tomcat 8.5.100 release that TuxCare onboarded. The fix adds validation to reject non-token characters in trailer header names and control characters (except HT) in trailer header values, preventing request smuggling attacks. Commit c83fe47725f7a...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2023-45648"
      },
      "impact_statement": "not_affected \u2014 Target Apache Tomcat 8.5.100 is NOT vulnerable to CVE-2023-45648. The upstream fix for HTTP trailer header validation was already present in the Apache Tomcat 8.5.100 release that TuxCare onboarded. The fix adds validation to reject non-token characters in trailer header names and control characters (except HT) in trailer header values, preventing request smuggling attacks. Commit c83fe47725f7a..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.apache.tomcat/tomcat-coyote@8.5.100.tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@8.5.100.tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-11-03T11:40:00.069704+00:00",
      "status_notes": "Vulnerability CVE-2023-46589 does not affect version 8.5.100.tuxcare.2 of org.apache.tomcat:tomcat-coyote. Apache Tomcat 8.5.100-tuxcare.10 is NOT AFFECTED by CVE-2023-46589. The target version 8.5.100 is after the fixed version 8.5.96, and the upstream Apache fix (commit c83fe47725 by Mark Thomas) was already present in the 8.5.100 release that TuxCare onboarded. The vulnerable pattern (missing character validation in HTTP trailer header parsing) is not present in the target code. Both critical validation checks are implemented: HttpParser.isToken() for header names (ChunkedInputFilter.java:576-578) and HttpParser.isControl() for header values (ChunkedInputFilter.java:642-643). The fix was authored by the upstream vendor (markt@apache.org), not by TuxCare, and was included in the base release.\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": "Apache Tomcat 8.5.100-tuxcare.10 is NOT AFFECTED by CVE-2023-46589. The target version 8.5.100 is after the fixed version 8.5.96, and the upstream Apache fix (commit c83fe47725 by Mark Thomas) was already present in the 8.5.100 release that TuxCare onboarded. The vulnerable pattern (missing character validation in HTTP trailer header parsing) is not present in the target code. Both critical validation checks are implemented: HttpParser.isToken() for header names (ChunkedInputFilter.java:576-578) and HttpParser.isControl() for header values (ChunkedInputFilter.java:642-643). The fix was authored by the upstream vendor (markt@apache.org), not by TuxCare, and was included in the base release.\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@8.5.100.tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@8.5.100.tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-11-02T18:41:44.135768+00:00",
      "status_notes": "Vulnerability CVE-2024-21733 does not affect version 8.5.100.tuxcare.2 of org.apache.tomcat:tomcat-coyote. not_affected \u2014 Target Apache Tomcat 8.5.100-tuxcare.10 is NOT AFFECTED by CVE-2024-21733. The vulnerability involves generation of error messages containing sensitive information when I/O is not allowed. The upstream Apache fix (commit 0ff1ed325d2a35c64a12c36f2bfd1959f66413f2 and 9b44626e136c89a107dd4458ad4bde6123359fd6, both authored by markt@apache.org in Feb 2021) was already included in the upstream Tomca...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2024-21733"
      },
      "impact_statement": "not_affected \u2014 Target Apache Tomcat 8.5.100-tuxcare.10 is NOT AFFECTED by CVE-2024-21733. The vulnerability involves generation of error messages containing sensitive information when I/O is not allowed. The upstream Apache fix (commit 0ff1ed325d2a35c64a12c36f2bfd1959f66413f2 and 9b44626e136c89a107dd4458ad4bde6123359fd6, both authored by markt@apache.org in Feb 2021) was already included in the upstream Tomca..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.apache.tomcat/tomcat-coyote@8.5.100.tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@8.5.100.tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2024-24549 does not affect version 8.5.100.tuxcare.2 of org.apache.tomcat:tomcat-coyote. The target (Apache Tomcat 8.5.100-tuxcare.10) is not affected by CVE-2024-24549. The vulnerability was fixed by upstream Apache in commit 0cac540a88 (authored by markt@apache.org on Jan 25, 2024) and included in the Apache Tomcat 8.5.100 release (tagged March 19, 2024). TuxCare adopted version 8.5.100 which already contained the fix. The vulnerable pattern (delayed validation of HTTP/2 headers until all frames are processed) is absent from the target code. CVE affects versions \"8.5.0 through 8.5.98\" and recommends upgrading to 8.5.99+; target is 8.5.100.",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2024-24549"
      },
      "impact_statement": "The target (Apache Tomcat 8.5.100-tuxcare.10) is not affected by CVE-2024-24549. The vulnerability was fixed by upstream Apache in commit 0cac540a88 (authored by markt@apache.org on Jan 25, 2024) and included in the Apache Tomcat 8.5.100 release (tagged March 19, 2024). TuxCare adopted version 8.5.100 which already contained the fix. The vulnerable pattern (delayed validation of HTTP/2 headers until all frames are processed) is absent from the target code. CVE affects versions \"8.5.0 through 8.5.98\" and recommends upgrading to 8.5.99+; target is 8.5.100."
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:maven/org.apache.tomcat/tomcat-coyote@8.5.100.tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@8.5.100.tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2024-34750 is fixed in version 8.5.100.tuxcare.2 of org.apache.tomcat:tomcat-coyote.",
      "vulnerability": {
        "name": "CVE-2024-34750"
      }
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:maven/org.apache.tomcat/tomcat-coyote@8.5.100.tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@8.5.100.tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2024-38286 is fixed in version 8.5.100.tuxcare.2 of org.apache.tomcat:tomcat-coyote.",
      "vulnerability": {
        "name": "CVE-2024-38286"
      }
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:maven/org.apache.tomcat/tomcat-coyote@8.5.100.tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@8.5.100.tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2024-52317 is fixed in version 8.5.100.tuxcare.2 of org.apache.tomcat:tomcat-coyote.",
      "vulnerability": {
        "name": "CVE-2024-52317"
      }
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:maven/org.apache.tomcat/tomcat-coyote@8.5.100.tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@8.5.100.tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2025-31650 is fixed in version 8.5.100.tuxcare.2 of org.apache.tomcat:tomcat-coyote.",
      "vulnerability": {
        "name": "CVE-2025-31650"
      }
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/org.apache.tomcat/tomcat-coyote@8.5.100.tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@8.5.100.tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2025-48989 affects version 8.5.100.tuxcare.2 of org.apache.tomcat:tomcat-coyote, and is fixed in 8.5.100-tuxcare.3.",
      "vulnerability": {
        "name": "CVE-2025-48989"
      },
      "action_statement": "Vulnerability CVE-2025-48989 affects version 8.5.100.tuxcare.2 of org.apache.tomcat:tomcat-coyote, and is fixed in 8.5.100-tuxcare.3."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/org.apache.tomcat/tomcat-coyote@8.5.100.tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@8.5.100.tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2025-52434 affects version 8.5.100.tuxcare.2 of org.apache.tomcat:tomcat-coyote, and is fixed in 8.5.100-tuxcare.4.",
      "vulnerability": {
        "name": "CVE-2025-52434"
      },
      "action_statement": "Vulnerability CVE-2025-52434 affects version 8.5.100.tuxcare.2 of org.apache.tomcat:tomcat-coyote, and is fixed in 8.5.100-tuxcare.4."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/org.apache.tomcat/tomcat-coyote@8.5.100.tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@8.5.100.tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2025-53506 affects version 8.5.100.tuxcare.2 of org.apache.tomcat:tomcat-coyote, and is fixed in 8.5.100-tuxcare.6.",
      "vulnerability": {
        "name": "CVE-2025-53506"
      },
      "action_statement": "Vulnerability CVE-2025-53506 affects version 8.5.100.tuxcare.2 of org.apache.tomcat:tomcat-coyote, and is fixed in 8.5.100-tuxcare.6."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/org.apache.tomcat/tomcat-coyote@8.5.100.tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@8.5.100.tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2025-66614 affects version 8.5.100.tuxcare.2 of org.apache.tomcat:tomcat-coyote, and is fixed in 8.5.100-tuxcare.8.",
      "vulnerability": {
        "name": "CVE-2025-66614"
      },
      "action_statement": "Vulnerability CVE-2025-66614 affects version 8.5.100.tuxcare.2 of org.apache.tomcat:tomcat-coyote, and is fixed in 8.5.100-tuxcare.8."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/org.apache.tomcat/tomcat-coyote@8.5.100.tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@8.5.100.tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2026-24733 affects version 8.5.100.tuxcare.2 of org.apache.tomcat:tomcat-coyote, and is fixed in 8.5.100-tuxcare.7.",
      "vulnerability": {
        "name": "CVE-2026-24733"
      },
      "action_statement": "Vulnerability CVE-2026-24733 affects version 8.5.100.tuxcare.2 of org.apache.tomcat:tomcat-coyote, and is fixed in 8.5.100-tuxcare.7."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/org.apache.tomcat/tomcat-coyote@8.5.100.tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@8.5.100.tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-10-28T21:58:36.804623+00:00",
      "status_notes": "Vulnerability CVE-2026-24734 affects version 8.5.100.tuxcare.2 of org.apache.tomcat:tomcat-coyote.",
      "vulnerability": {
        "name": "CVE-2026-24734"
      },
      "action_statement": "Vulnerability CVE-2026-24734 affects version 8.5.100.tuxcare.2 of org.apache.tomcat:tomcat-coyote."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/org.apache.tomcat/tomcat-coyote@8.5.100.tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@8.5.100.tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2026-24880 affects version 8.5.100.tuxcare.2 of org.apache.tomcat:tomcat-coyote, and is fixed in 8.5.100-tuxcare.10.",
      "vulnerability": {
        "name": "CVE-2026-24880"
      },
      "action_statement": "Vulnerability CVE-2026-24880 affects version 8.5.100.tuxcare.2 of org.apache.tomcat:tomcat-coyote, and is fixed in 8.5.100-tuxcare.10."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.apache.tomcat/tomcat-coyote@8.5.100.tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@8.5.100.tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-11-03T16:29:44.182918+00:00",
      "status_notes": "Vulnerability CVE-2026-29129 does not affect version 8.5.100.tuxcare.2 of org.apache.tomcat:tomcat-coyote. not_affected \u2014 Apache Tomcat 8.5.100 is NOT affected by CVE-2026-29129. The vulnerability was introduced in newer versions (9.0.114-115, 10.1.51-52, 11.0.16-18) when TLS 1.3 specific cipher configuration was added. The vulnerable code pattern (using HashSet to combine TLS 1.3 and legacy cipher lists, losing configured preference order) does not exist in version 8.5.100, which lacks separate TLS 1.3 cipher con...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2026-29129"
      },
      "impact_statement": "not_affected \u2014 Apache Tomcat 8.5.100 is NOT affected by CVE-2026-29129. The vulnerability was introduced in newer versions (9.0.114-115, 10.1.51-52, 11.0.16-18) when TLS 1.3 specific cipher configuration was added. The vulnerable code pattern (using HashSet to combine TLS 1.3 and legacy cipher lists, losing configured preference order) does not exist in version 8.5.100, which lacks separate TLS 1.3 cipher con..."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/org.apache.tomcat/tomcat-coyote@8.5.100.tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@8.5.100.tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2026-32990 affects version 8.5.100.tuxcare.2 of org.apache.tomcat:tomcat-coyote.",
      "vulnerability": {
        "name": "CVE-2026-32990"
      },
      "action_statement": "Vulnerability CVE-2026-32990 affects version 8.5.100.tuxcare.2 of org.apache.tomcat:tomcat-coyote."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/org.apache.tomcat/tomcat-coyote@8.5.100.tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@8.5.100.tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2026-41293 affects version 8.5.100.tuxcare.2 of org.apache.tomcat:tomcat-coyote.",
      "vulnerability": {
        "name": "CVE-2026-41293"
      },
      "action_statement": "Vulnerability CVE-2026-41293 affects version 8.5.100.tuxcare.2 of org.apache.tomcat:tomcat-coyote."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.apache.tomcat/tomcat-coyote@8.5.100.tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@8.5.100.tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-11-06T17:20:00.095414+00:00",
      "status_notes": "Vulnerability CVE-2026-65637 does not affect version 8.5.100.tuxcare.2 of org.apache.tomcat:tomcat-coyote. Prechecker: No vulnerable code from the fix was found, and this version implements the code the fix changes differently from upstream. Version 8.5.100 is on an older release line than any version the advisories list as affected. Advisories: GitHub GHSA-f525-44xv-f2qj (newer lines only), NVD (newer lines only), CVE record (newer lines only).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2026-65637"
      },
      "impact_statement": "Prechecker: No vulnerable code from the fix was found, and this version implements the code the fix changes differently from upstream. Version 8.5.100 is on an older release line than any version the advisories list as affected. Advisories: GitHub GHSA-f525-44xv-f2qj (newer lines only), NVD (newer lines only), CVE record (newer lines only)."
    }
  ]
}
