{
  "@id": "urn:uuid:1ea89576-61dd-4361-ab80-3c7adc96c862",
  "role": "Document Creator",
  "author": "https://tuxcare.com",
  "version": 16,
  "@context": "https://openvex.dev/ns/v0.2.0",
  "timestamp": "2026-10-30T01:45:09.863951+00:00",
  "statements": [
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-util@11.0.28.tuxcare0004",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-util@11.0.28.tuxcare0004"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2026-8384 does not affect version 11.0.28.tuxcare0004 of org.eclipse.jetty:jetty-util. 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..."
    }
  ]
}