{
  "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json",
  "bomFormat": "CycloneDX",
  "specVersion": "1.6",
  "serialNumber": "urn:uuid:a464bc35-3b4a-507b-94fc-408141f2900d",
  "version": 1,
  "metadata": {
    "supplier": {
      "name": "TuxCare",
      "url": [
        "https://tuxcare.com"
      ]
    }
  },
  "components": [
    {
      "name": "tomcat-coyote",
      "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@7.0.70-tuxcare.8",
      "type": "library",
      "group": "org.apache.tomcat",
      "bom-ref": "pkg:maven/org.apache.tomcat/tomcat-coyote@7.0.70-tuxcare.8",
      "version": "7.0.70-tuxcare.8",
      "pedigree": {
        "ancestors": [
          {
            "name": "tomcat-coyote",
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote@7.0.70",
            "type": "library",
            "group": "org.apache.tomcat",
            "version": "7.0.70"
          }
        ]
      },
      "supplier": {
        "url": [
          "https://tuxcare.com"
        ],
        "name": "TuxCare"
      }
    }
  ],
  "vulnerabilities": [
    {
      "id": "CVE-2012-5568",
      "affects": [
        {
          "ref": "pkg:maven/org.apache.tomcat/tomcat-coyote@7.0.70-tuxcare.8"
        }
      ],
      "bom-ref": "urn:uuid:df213617-edb0-582b-9e93-6ce6be3adddb",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2012-5568 affects version 7.0.70-tuxcare.8 of org.apache.tomcat:tomcat-coyote and will not be fixed. Apache does not treat CVE-2012-5568 as a Tomcat vulnerability and ships no fix; mitigation is connector configuration.",
        "response": [
          "will_not_fix"
        ]
      }
    },
    {
      "id": "CVE-2014-0095",
      "affects": [
        {
          "ref": "pkg:maven/org.apache.tomcat/tomcat-coyote@7.0.70-tuxcare.8"
        }
      ],
      "bom-ref": "urn:uuid:f3cddbc0-7d49-54e0-9397-7d7ed9e52491",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2014-0095 does not affect version 7.0.70-tuxcare.8 of org.apache.tomcat:tomcat-coyote. not_affected \u2014 CVE-2014-0095 affects Apache Tomcat 8.x before 8.0.4 and was a regression introduced in Tomcat 8.0.0-RC2 as part of Servlet 3.1 non-blocking IO support. The vulnerability caused thread hangs when processing AJP requests with Content-Length: 0. Tomcat 7.0.70 does not have the vulnerable code pattern because it lacks the optimization that was introduced in Tomcat 8.x. Tomcat 7.x always sends expl...",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2016-6816",
      "affects": [
        {
          "ref": "pkg:maven/org.apache.tomcat/tomcat-coyote@7.0.70-tuxcare.8"
        }
      ],
      "bom-ref": "urn:uuid:35d65c09-e3c1-5272-8f78-b9241c7dd61d",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2016-6816 is fixed in version 7.0.70-tuxcare.8 of org.apache.tomcat:tomcat-coyote."
      }
    },
    {
      "id": "CVE-2017-5651",
      "affects": [
        {
          "ref": "pkg:maven/org.apache.tomcat/tomcat-coyote@7.0.70-tuxcare.8"
        }
      ],
      "bom-ref": "urn:uuid:40da5e82-447b-5b74-a5c9-35e33ffadb9c",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2017-5651 does not affect version 7.0.70-tuxcare.8 of org.apache.tomcat:tomcat-coyote. Tomcat 7.0.70 is not affected by CVE-2017-5651. This vulnerability was introduced during the HTTP connector refactoring for Tomcat 8.5.x onwards and does not exist in Tomcat 7.x. The target uses a pre-refactoring architecture with separate sendfile state tracking via the `sendfileInProgress` boolean flag, which inherently prevents the race condition that allows a Processor to be added to the cache twice. The vulnerable code pattern (relying solely on `sendfileData != null` for state determination) is not present in version 7.0.70.",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2019-0199",
      "affects": [
        {
          "ref": "pkg:maven/org.apache.tomcat/tomcat-coyote@7.0.70-tuxcare.8"
        }
      ],
      "bom-ref": "urn:uuid:8e8241b8-aedc-57d2-956b-a01cc7ae288f",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2019-0199 does not affect version 7.0.70-tuxcare.8 of org.apache.tomcat:tomcat-coyote. pre-checker-haiku: not_affected \u2014 A1: The fix protects the HTTP/2 implementation against clients that send excessive SETTINGS frames and hold streams open without reading or writing, using stream timeouts, overhead tracking and a CloseNowException path. This tree has no HTTP/2 code at all: no coyote/http2 package, no Http2Protocol or UpgradeProtocol, no SETTINGS or frame parsing, and no CloseNowException class or thrower. So no...",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2019-2684",
      "affects": [
        {
          "ref": "pkg:maven/org.apache.tomcat/tomcat-coyote@7.0.70-tuxcare.8"
        }
      ],
      "bom-ref": "urn:uuid:b3962d2d-83af-5474-8d2a-f02c949a1fbf",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2019-2684 is fixed in version 7.0.70-tuxcare.8 of org.apache.tomcat:tomcat-coyote."
      }
    },
    {
      "id": "CVE-2020-13934",
      "affects": [
        {
          "ref": "pkg:maven/org.apache.tomcat/tomcat-coyote@7.0.70-tuxcare.8"
        }
      ],
      "bom-ref": "urn:uuid:b89a09f5-b00d-5570-bb9f-f6b2057c51c0",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2020-13934 does not affect version 7.0.70-tuxcare.8 of org.apache.tomcat:tomcat-coyote. Tomcat 7.0.70 is not affected by CVE-2020-13934. The vulnerability requires HTTP/2 (h2c) protocol support to leak HTTP/1.1 processors during direct h2c connections. HTTP/2 support was first introduced in Tomcat 8.5/9.0 (circa 2016), and version 7.0.70 predates this feature entirely. The target codebase contains no HTTP/2 implementation, no h2c upgrade handling, and no UpgradeProtocol interface used by the vulnerable code pattern.",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2020-13943",
      "affects": [
        {
          "ref": "pkg:maven/org.apache.tomcat/tomcat-coyote@7.0.70-tuxcare.8"
        }
      ],
      "bom-ref": "urn:uuid:3478fcbc-371e-50c0-8331-ab359c40884b",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2020-13943 does not affect version 7.0.70-tuxcare.8 of org.apache.tomcat:tomcat-coyote. not_affected \u2014 The target repository (Apache Tomcat 7.0.70 at commit a78de4bfa3) does not contain HTTP/2 protocol support. CVE-2020-13943 affects the HTTP/2 implementation in the org.apache.coyote.http2 package, which does not exist in this version. HTTP/2 support was introduced in Tomcat 8.5.0+; version 7.0.70 only supports HTTP/1.1 and AJP protocols. The vulnerability's attack vector (HTTP/2 HEADERS frames ...",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2020-17527",
      "affects": [
        {
          "ref": "pkg:maven/org.apache.tomcat/tomcat-coyote@7.0.70-tuxcare.8"
        }
      ],
      "bom-ref": "urn:uuid:edc02ec4-e710-5c86-b5f9-c4fc22361bb7",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2020-17527 does not affect version 7.0.70-tuxcare.8 of org.apache.tomcat:tomcat-coyote. vc: not_affected \u2014 Target is Apache Tomcat 7.0.70, the same product as the CVE but a release line with no HTTP/2 support. The org.apache.coyote.http2 package, HPACK decoder and h2c/HTTP/2 upgrade handling do not exist in the tree, so the HTTP/2 header-reuse flaw (CVE-2020-17527) cannot occur. This is not a false positive: the product is Tomcat in both cases.",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2021-25122",
      "affects": [
        {
          "ref": "pkg:maven/org.apache.tomcat/tomcat-coyote@7.0.70-tuxcare.8"
        }
      ],
      "bom-ref": "urn:uuid:8a4fcb3a-75d4-5491-9a35-215dac338bce",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2021-25122 does not affect version 7.0.70-tuxcare.8 of org.apache.tomcat:tomcat-coyote. vc: not_affected \u2014 The advisory is for Apache Tomcat and this repo is Apache Tomcat 7.0.70, so it is not a false positive. The flaw is in HTTP/2 cleartext (h2c) upgrade handling, and Tomcat 7.0.x has no HTTP/2 or h2c code at all. The affected ranges in the CVE (8.5.0-8.5.61, 9.0.0.M1-9.0.41, 10.0.0-M1-10.0.0) also exclude 7.x. The target is not affected.",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2022-42252",
      "affects": [
        {
          "ref": "pkg:maven/org.apache.tomcat/tomcat-coyote@7.0.70-tuxcare.8"
        }
      ],
      "bom-ref": "urn:uuid:db556f30-2440-56db-b266-4756221a80df",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2022-42252 affects version 7.0.70-tuxcare.8 of org.apache.tomcat:tomcat-coyote."
      }
    },
    {
      "id": "CVE-2023-24998",
      "affects": [
        {
          "ref": "pkg:maven/org.apache.tomcat/tomcat-coyote@7.0.70-tuxcare.8"
        }
      ],
      "bom-ref": "urn:uuid:5084a99a-3d58-5eeb-9c49-f22f7b5e4a48",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2023-24998 is fixed in version 7.0.70-tuxcare.8 of org.apache.tomcat:tomcat-coyote."
      }
    },
    {
      "id": "CVE-2023-28709",
      "affects": [
        {
          "ref": "pkg:maven/org.apache.tomcat/tomcat-coyote@7.0.70-tuxcare.8"
        }
      ],
      "bom-ref": "urn:uuid:9117fc85-e7b1-5d1e-924d-8018e9a1cfb7",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2023-28709 is fixed in version 7.0.70-tuxcare.8 of org.apache.tomcat:tomcat-coyote."
      }
    },
    {
      "id": "CVE-2023-34981",
      "affects": [
        {
          "ref": "pkg:maven/org.apache.tomcat/tomcat-coyote@7.0.70-tuxcare.8"
        }
      ],
      "bom-ref": "urn:uuid:10ac1f44-6c13-549b-86ed-1e4a6fb3b488",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2023-34981 does not affect version 7.0.70-tuxcare.8 of org.apache.tomcat:tomcat-coyote. pre-checker-haiku: not_affected \u2014 B: The fix guarantees that every AJP response carries a SEND_HEADERS packet even when it has no HTTP headers, which the regressed loop in upstream lacked. In this tree, AbstractAjpProcessor.prepareResponse writes the SEND_HEADERS header byte unconditionally before any header loop and then writes the header count, which may be zero, so a response with no headers still sends the packet and the pr...",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2023-42794",
      "affects": [
        {
          "ref": "pkg:maven/org.apache.tomcat/tomcat-coyote@7.0.70-tuxcare.8"
        }
      ],
      "bom-ref": "urn:uuid:11c3635a-d817-5973-960e-cba27b5075ea",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2023-42794 does not affect version 7.0.70-tuxcare.8 of org.apache.tomcat:tomcat-coyote. not_affected \u2014 Tomcat 7.0.70 is NOT affected by CVE-2023-42794. The vulnerability exists in Tomcat 9.0.70-9.0.80 and 8.5.85-8.5.93 where an in-progress refactoring completely removed the finalize() method, preventing temporary file cleanup during garbage collection. Version 7.0.70 retains a functional finalize() method (lines 552-559 of DiskFileItem.java) that successfully deletes temporary files when objects...",
        "justification": "code_not_reachable"
      }
    },
    {
      "id": "CVE-2023-44487",
      "affects": [
        {
          "ref": "pkg:maven/org.apache.tomcat/tomcat-coyote@7.0.70-tuxcare.8"
        }
      ],
      "bom-ref": "urn:uuid:66e77a52-1e27-517f-b87e-23c2991b20dc",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2023-44487 does not affect version 7.0.70-tuxcare.8 of org.apache.tomcat:tomcat-coyote. vc: not_affected \u2014 Tomcat 7.0.70 has no HTTP/2 implementation: no h2/h2c, ALPN-based protocol negotiation, HPACK, frame parser or stream multiplexing. HTTP/2 Rapid Reset (CVE-2023-44487) therefore has no input path in this tree. This is the same product lineage as the Tomcat fix commits, so it is not a false positive. It is not affected (Type A1, input absent).",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2023-45648",
      "affects": [
        {
          "ref": "pkg:maven/org.apache.tomcat/tomcat-coyote@7.0.70-tuxcare.8"
        }
      ],
      "bom-ref": "urn:uuid:5eb6d23e-a583-5666-ac0e-f42d8d784844",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2023-45648 affects version 7.0.70-tuxcare.8 of org.apache.tomcat:tomcat-coyote."
      }
    },
    {
      "id": "CVE-2023-46589",
      "affects": [
        {
          "ref": "pkg:maven/org.apache.tomcat/tomcat-coyote@7.0.70-tuxcare.8"
        }
      ],
      "bom-ref": "urn:uuid:85da9bb3-ef55-5ad6-9f80-80288e292b8d",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2023-46589 affects version 7.0.70-tuxcare.8 of org.apache.tomcat:tomcat-coyote."
      }
    },
    {
      "id": "CVE-2024-21733",
      "affects": [
        {
          "ref": "pkg:maven/org.apache.tomcat/tomcat-coyote@7.0.70-tuxcare.8"
        }
      ],
      "bom-ref": "urn:uuid:be62e1ab-758f-5629-96cc-a346284b665a",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2024-21733 does not affect version 7.0.70-tuxcare.8 of org.apache.tomcat:tomcat-coyote. Re-checked 2026-11-10 by the vulnerability checker and confirmed by an independent code review: not affected. This version is not affected because failed reads do not expose stale request-buffer data. In java/org/apache/coyote/http11/InternalNioInputBuffer.java:441, only successfully read bytes are copied and added to the readable bounds. Body reads reset buffer positions before reading (java/org/apache/coyote/http11/InternalNioInputBuffer.java:800) and return only valid unread bytes (java/org/apache/coyote/http11/InternalNioInputBuffer.java:826).",
        "justification": "code_not_reachable"
      }
    },
    {
      "id": "CVE-2024-24549",
      "affects": [
        {
          "ref": "pkg:maven/org.apache.tomcat/tomcat-coyote@7.0.70-tuxcare.8"
        }
      ],
      "bom-ref": "urn:uuid:66cb765d-b33f-5e3b-808c-7822068eceef",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2024-24549 does not affect version 7.0.70-tuxcare.8 of org.apache.tomcat:tomcat-coyote. Tomcat 7.0.70 is not affected by CVE-2024-24549. This vulnerability is specific to HTTP/2 header processing in Apache Tomcat, where streams were not reset until after all headers (including CONTINUATION frames) were processed when limits were exceeded. HTTP/2 support was introduced in Tomcat 8.5.0, and version 7.0.70 predates this feature entirely. The target codebase contains only HTTP/1.1 and AJP protocol implementations, which already enforce header size limits incrementally during parsing, not after completion.",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2024-34750",
      "affects": [
        {
          "ref": "pkg:maven/org.apache.tomcat/tomcat-coyote@7.0.70-tuxcare.8"
        }
      ],
      "bom-ref": "urn:uuid:3a4b8f0c-b8dd-55cf-a66c-100351bfe54c",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2024-34750 does not affect version 7.0.70-tuxcare.8 of org.apache.tomcat:tomcat-coyote. vc: not_affected \u2014 Target is Apache Tomcat 7.0.70, the same product lineage as the CVE. Tomcat 7.0.x has no HTTP/2 support: there is no org.apache.coyote.http2 package, no Http2UpgradeHandler, no stream or HPACK code. The CVE-2024-34750 flaw (HTTP/2 stream miscounting leading to an infinite timeout) needs HTTP/2 stream accounting, which is absent. The listed CVE range also starts at 8.5, and HTTP/2 arrived in 8.5...",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2024-38286",
      "affects": [
        {
          "ref": "pkg:maven/org.apache.tomcat/tomcat-coyote@7.0.70-tuxcare.8"
        }
      ],
      "bom-ref": "urn:uuid:beb953a0-f9cd-5984-b887-c96400931de5",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2024-38286 affects version 7.0.70-tuxcare.8 of org.apache.tomcat:tomcat-coyote."
      }
    },
    {
      "id": "CVE-2024-52317",
      "affects": [
        {
          "ref": "pkg:maven/org.apache.tomcat/tomcat-coyote@7.0.70-tuxcare.8"
        }
      ],
      "bom-ref": "urn:uuid:45f67c35-52f2-5329-9c42-6a5a9acba3f5",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2024-52317 does not affect version 7.0.70-tuxcare.8 of org.apache.tomcat:tomcat-coyote. not_affected \u2014 Tomcat 7.0.70 is not affected by CVE-2024-52317 because it does not have HTTP/2 support. The vulnerability exists in HTTP/2 stream recycling logic (org.apache.coyote.http2.Stream and StreamProcessor classes) which was introduced in Tomcat 8.5+. The entire HTTP/2 implementation is absent from Tomcat 7.x. Exhaustive search confirmed no http2 package, no vulnerable Stream/StreamProcessor classes, ...",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2025-31650",
      "affects": [
        {
          "ref": "pkg:maven/org.apache.tomcat/tomcat-coyote@7.0.70-tuxcare.8"
        }
      ],
      "bom-ref": "urn:uuid:c66d393e-701b-5067-9f2b-8a09bde09700",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2025-31650 does not affect version 7.0.70-tuxcare.8 of org.apache.tomcat:tomcat-coyote. Apache Tomcat 7.0.70 is NOT affected by CVE-2025-31650. This vulnerability targets HTTP/2 priority header parsing code that does not exist in Tomcat 7.0.x. HTTP/2 support was added in Tomcat 8.5+. The target lacks all HTTP/2 infrastructure (no http2 package, no Priority parsing, no HTTP/2 upgrade handlers), so the vulnerable INPUT type (invalid HTTP/2 priority headers/frames) is never received by the target codebase.",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2025-48989",
      "affects": [
        {
          "ref": "pkg:maven/org.apache.tomcat/tomcat-coyote@7.0.70-tuxcare.8"
        }
      ],
      "bom-ref": "urn:uuid:682e5516-a49d-5db9-a05c-d6445c37f017",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2025-48989 does not affect version 7.0.70-tuxcare.8 of org.apache.tomcat:tomcat-coyote. vc: not_affected \u2014 Target is Apache Tomcat 7.0.70, the same product as the CVE. HTTP/2 support (coyote.http2, h2c upgrade, ALPN, stream/RST_STREAM handling) was introduced in Tomcat 8.5/9 and is absent from this tree, so the MadeYouReset flow cannot occur. Not a false positive (same product lineage). Not already_fixed: there is no CVE-2025-48989 backport on this branch (only on 9.0.x/10.1.x branches).",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2025-52434",
      "affects": [
        {
          "ref": "pkg:maven/org.apache.tomcat/tomcat-coyote@7.0.70-tuxcare.8"
        }
      ],
      "bom-ref": "urn:uuid:2d1d2add-d666-5e7a-8bda-11e1dcaa3917",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2025-52434 does not affect version 7.0.70-tuxcare.8 of org.apache.tomcat:tomcat-coyote. vc: not_affected \u2014 Tomcat 7.0.70 has no HTTP/2 code, and its APR connector uses a different design from the 8.5/9.0 code that CVE-2025-52434 fixes. The racy APR socket-wrapper code that the upstream fix and the TuxCare backports to other branches change is absent. A native APR socket is serialized by the per-wrapper monitor, one-shot poller registration and a deferred destroy on the Poller thread, so a concurrent...",
        "justification": "protected_at_runtime"
      }
    },
    {
      "id": "CVE-2025-53506",
      "affects": [
        {
          "ref": "pkg:maven/org.apache.tomcat/tomcat-coyote@7.0.70-tuxcare.8"
        }
      ],
      "bom-ref": "urn:uuid:597b8164-6dad-5d01-8ac5-80e22ddd6abd",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2025-53506 does not affect version 7.0.70-tuxcare.8 of org.apache.tomcat:tomcat-coyote. vc: not_affected \u2014 Target is Apache Tomcat 7.0.70 (TuxCare build). It has no HTTP/2 implementation, so CVE-2025-53506 (HTTP/2 concurrent-streams limit enforced only after SETTINGS ack) cannot apply. The product matches, so this is not a false positive.",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2025-66614",
      "affects": [
        {
          "ref": "pkg:maven/org.apache.tomcat/tomcat-coyote@7.0.70-tuxcare.8"
        }
      ],
      "bom-ref": "urn:uuid:1eb39238-134a-5c09-9cf8-a94b8ad8f519",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2025-66614 does not affect version 7.0.70-tuxcare.8 of org.apache.tomcat:tomcat-coyote. Tomcat 7.0.70 is not affected by CVE-2025-66614. The vulnerability requires SNI (Server Name Indication) support to extract the TLS SNI hostname and SSLHostConfig-based per-virtual-host TLS configurations to enable different client certificate authentication requirements per virtual host. Tomcat 7.0.70 does not support SNI - this feature was introduced in Tomcat 8.5 (confirmed by the target's own documentation in ssl-howto.xml). The CVE explicitly states \"Older EOL versions are not affected\", and version 7.0.70 predates the 8.5.0 threshold. Code analysis confirms no SNI extraction code, no SSLHostConfig class, and no Java SNI APIs are present in 7.0.70.",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2026-24733",
      "affects": [
        {
          "ref": "pkg:maven/org.apache.tomcat/tomcat-coyote@7.0.70-tuxcare.8"
        }
      ],
      "bom-ref": "urn:uuid:3798a4e7-e772-56e8-84f2-e129eceda791",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-24733 is fixed in version 7.0.70-tuxcare.8 of org.apache.tomcat:tomcat-coyote."
      }
    },
    {
      "id": "CVE-2026-24734",
      "affects": [
        {
          "ref": "pkg:maven/org.apache.tomcat/tomcat-coyote@7.0.70-tuxcare.8"
        }
      ],
      "bom-ref": "urn:uuid:faf22d0e-940b-5186-a31c-d22ab229df44",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-24734 does not affect version 7.0.70-tuxcare.8 of org.apache.tomcat:tomcat-coyote. vc: not_affected \u2014 Target is Apache Tomcat 7.0.70 (same product lineage, so not a false positive). It contains no OCSP code at all. The CVE concerns the OCSP verification code in Tomcat Native and in Tomcat's FFM (Panama) port, which exists only in Tomcat 9.0.83+, 10.1.x and 11.x. The tomcat-native C source is not in this repo, and the Java JNI wrappers contain no OCSP handling. Rule 5 Type A1 applies: the Input ...",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2026-24880",
      "affects": [
        {
          "ref": "pkg:maven/org.apache.tomcat/tomcat-coyote@7.0.70-tuxcare.8"
        }
      ],
      "bom-ref": "urn:uuid:1fd8b4f5-1ec5-5d5c-99d3-11f35ca26f4a",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-24880 is fixed in version 7.0.70-tuxcare.8 of org.apache.tomcat:tomcat-coyote."
      }
    },
    {
      "id": "CVE-2026-29129",
      "affects": [
        {
          "ref": "pkg:maven/org.apache.tomcat/tomcat-coyote@7.0.70-tuxcare.8"
        }
      ],
      "bom-ref": "urn:uuid:983050e6-0a65-5e50-b2e7-93d12bfc3b28",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-29129 does not affect version 7.0.70-tuxcare.8 of org.apache.tomcat:tomcat-coyote. not_affected \u2014 Apache Tomcat 7.0.70 is NOT affected by CVE-2026-29129. The vulnerability was introduced in later versions (9.0.114+, 10.1.51+, 11.0.16+) when TLS 1.3 cipher configuration support was added. The bug occurred in SSLHostConfig.getJsseCipherNames() which used HashSet instead of LinkedHashSet, causing configured cipher order to be lost. Tomcat 7.0.70 does not have the SSLHostConfig class or TLS 1.3...",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2026-32990",
      "affects": [
        {
          "ref": "pkg:maven/org.apache.tomcat/tomcat-coyote@7.0.70-tuxcare.8"
        }
      ],
      "bom-ref": "urn:uuid:542c6914-f3cd-5264-b42b-c0f16f2c9093",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-32990 does not affect version 7.0.70-tuxcare.8 of org.apache.tomcat:tomcat-coyote. not_affected \u2014 Tomcat 7.0.70 is not affected by CVE-2026-32990. The vulnerability exists in the SNI (Server Name Indication) hostname validation code (checkSni method in AbstractEndpoint.java) which performs case-sensitive comparison when looking up SSL configurations. This SNI validation architecture, including the SSLHostConfig class and checkSni method, was introduced in Tomcat 8.5+ and does not exist in T...",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2026-41293",
      "affects": [
        {
          "ref": "pkg:maven/org.apache.tomcat/tomcat-coyote@7.0.70-tuxcare.8"
        }
      ],
      "bom-ref": "urn:uuid:e760d0ad-2afb-58bf-9063-731722eaed80",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-41293 does not affect version 7.0.70-tuxcare.8 of org.apache.tomcat:tomcat-coyote. Tomcat 7.0.70 is not affected by CVE-2026-41293. The vulnerability concerns improper character validation in HTTP/2 HPACK header decoding. Tomcat 7.0.70 does not include HTTP/2 protocol support - it only supports HTTP/1.1 and AJP. HTTP/2 support was introduced in Tomcat 8.5 and later versions. The vulnerable code (HPackHuffman, HpackDecoder, Http2Parser classes and associated validation methods) is entirely absent from this version. Exhaustive search confirmed no http2 package, no HTTP/2 Java files, and no HTTP/2 protocol handlers exist in the codebase.",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2026-65637",
      "affects": [
        {
          "ref": "pkg:maven/org.apache.tomcat/tomcat-coyote@7.0.70-tuxcare.8"
        }
      ],
      "bom-ref": "urn:uuid:7fb7b704-9727-55f3-9d83-f5241d32a403",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-65637 does not affect version 7.0.70-tuxcare.8 of org.apache.tomcat:tomcat-coyote. Prechecker: No vulnerable code from the fix was found; the fixed code and the component it belongs to are absent from this version. Version 7.0.70 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": "code_not_present"
      }
    }
  ],
  "dependencies": [
    {
      "ref": "pkg:maven/org.apache.tomcat/tomcat-coyote@7.0.70-tuxcare.8"
    }
  ]
}