{
  "@id": "urn:uuid:1b73e000-ec89-430c-ac70-58f8966c028a",
  "role": "Document Creator",
  "author": "https://tuxcare.com",
  "version": 14,
  "@context": "https://openvex.dev/ns/v0.2.0",
  "timestamp": "2026-10-30T01:45:09.863951+00:00",
  "statements": [
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-proxy@11.0.28.tuxcare0005",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-proxy@11.0.28.tuxcare0005"
          }
        }
      ],
      "timestamp": "2026-10-28T00:31:22.764938+00:00",
      "status_notes": "Vulnerability CVE-2026-18660 affects version 11.0.28.tuxcare0005 of org.eclipse.jetty:jetty-proxy.",
      "vulnerability": {
        "name": "CVE-2026-18660"
      },
      "action_statement": "Vulnerability CVE-2026-18660 affects version 11.0.28.tuxcare0005 of org.eclipse.jetty:jetty-proxy."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-proxy@11.0.28.tuxcare0005",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-proxy@11.0.28.tuxcare0005"
          }
        }
      ],
      "timestamp": "2026-10-28T00:31:22.764938+00:00",
      "status_notes": "Vulnerability CVE-2026-8384 does not affect version 11.0.28.tuxcare0005 of org.eclipse.jetty:jetty-proxy. not_affected \u2014 Jetty 11.0.28 is not affected by CVE-2026-8384. While the target contains similar semicolon-handling code in decodePath() that doesn't update the character tracking variable, the vulnerability does not manifest due to architectural differences. Jetty 11 uses a two-stage normalization process (decodePath then canonicalPath) where the path is always fully normalized before security checks, unlike...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2026-8384"
      },
      "impact_statement": "not_affected \u2014 Jetty 11.0.28 is not affected by CVE-2026-8384. While the target contains similar semicolon-handling code in decodePath() that doesn't update the character tracking variable, the vulnerability does not manifest due to architectural differences. Jetty 11 uses a two-stage normalization process (decodePath then canonicalPath) where the path is always fully normalized before security checks, unlike..."
    }
  ]
}