{
  "@id": "urn:uuid:7866a2f6-a430-47c2-9114-b5449878179c",
  "role": "Document Creator",
  "author": "https://tuxcare.com",
  "version": 38,
  "@context": "https://openvex.dev/ns/v0.2.0",
  "timestamp": "2026-11-04T03:18:33.007797+00:00",
  "statements": [
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/org.apache.tomcat/tomcat-coyote-ffm@9.0.100-tuxcare.6",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote-ffm@9.0.100-tuxcare.6"
          }
        }
      ],
      "timestamp": "2026-11-04T03:18:33.007797+00:00",
      "status_notes": "Vulnerability CVE-2026-24734 affects version 9.0.100-tuxcare.6 of org.apache.tomcat:tomcat-coyote-ffm.",
      "vulnerability": {
        "name": "CVE-2026-24734"
      },
      "action_statement": "Vulnerability CVE-2026-24734 affects version 9.0.100-tuxcare.6 of org.apache.tomcat:tomcat-coyote-ffm."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.apache.tomcat/tomcat-coyote-ffm@9.0.100-tuxcare.6",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote-ffm@9.0.100-tuxcare.6"
          }
        }
      ],
      "timestamp": "2026-10-25T20:17:00.165429+00:00",
      "status_notes": "Vulnerability CVE-2026-29145 does not affect version 9.0.100-tuxcare.6 of org.apache.tomcat:tomcat-coyote-ffm. Tomcat 9.0.100 is not affected by CVE-2026-29145. The flaw is that the FFM OpenSSL verify callback accepts non-SUCCESSFUL OCSP responses (e.g. TRY_LATER). On 9.0.100 the check in OpenSSLEngine still rejects them (UNKNOWN status with errnum <= 0 fails the handshake). The lenient check that caused the flaw (upstream 4881026c62, first in 9.0.111) is not present. The upstream fix d1406df5ae only re-codes these responses as X509_V_ERR_UNABLE_TO_GET_CRL for the ocspSoftFail switch added in 9.0.116, which 9.0.100 does not have. Applied to 9.0.100, that patch would turn the reject into an accept, as reproduced in docker with a TRY_LATER OCSP responder. The same backport was reverted on 10.1.42 (!331). No code change is needed.",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2026-29145"
      },
      "impact_statement": "Tomcat 9.0.100 is not affected by CVE-2026-29145. The flaw is that the FFM OpenSSL verify callback accepts non-SUCCESSFUL OCSP responses (e.g. TRY_LATER). On 9.0.100 the check in OpenSSLEngine still rejects them (UNKNOWN status with errnum <= 0 fails the handshake). The lenient check that caused the flaw (upstream 4881026c62, first in 9.0.111) is not present. The upstream fix d1406df5ae only re-codes these responses as X509_V_ERR_UNABLE_TO_GET_CRL for the ocspSoftFail switch added in 9.0.116, which 9.0.100 does not have. Applied to 9.0.100, that patch would turn the reject into an accept, as reproduced in docker with a TRY_LATER OCSP responder. The same backport was reverted on 10.1.42 (!331). No code change is needed."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/org.apache.tomcat/tomcat-coyote-ffm@9.0.100-tuxcare.6",
          "identifiers": {
            "purl": "pkg:maven/org.apache.tomcat/tomcat-coyote-ffm@9.0.100-tuxcare.6"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2026-34500 affects version 9.0.100-tuxcare.6 of org.apache.tomcat:tomcat-coyote-ffm.",
      "vulnerability": {
        "name": "CVE-2026-34500"
      },
      "action_statement": "Vulnerability CVE-2026-34500 affects version 9.0.100-tuxcare.6 of org.apache.tomcat:tomcat-coyote-ffm."
    }
  ]
}
