CVE-2026-8384
Eclipse Jetty 12.0.0 – 12.0.35
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:NSummary
CVE-2026-8384 is a medium-severity Use of Non-Canonical URL Paths for Authorization Decisions (CWE-647) vulnerability in Eclipse Jetty. Its CVSS base score is 5.3 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 14th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-43647
Vulnerability Data
In Eclipse Jetty, an HTTP URI of this form: /public;/../admin/secret.txt results in an unresolved path of: /public/../admin/secret.txt instead of the expected: /admin/secret.txt Jetty itself is not affected, as it will not serve the secret.txt file because it will not pass…
more
the alias checker (only resolved resources are served). However, web applications that rely on resolved paths being provided by Jetty may be confused when receiving an unresolved path.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise TechniquesAI
Why these techniques?
Path normalization flaw (CWE-647) in public-facing Jetty server enables potential unauthorized file access or bypass in dependent web apps.
Likely ATT&CK TechniquesAI
Techniques this vulnerability likely enables, inferred from its description, weakness type, and attributed-actor tradecraft. Confidence is per-technique.
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V2.2.1V10.4.1
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Enforcing well-defined authorization policies prevents URL canonicalization bypasses when path handling is included in the implementation.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can discover non-canonical URL bypasses but does not itself implement the preventive control.
Defining application security requirements that mandate canonical URL handling and authorization checks mitigates the weakness at design time.
Secure-coding standards that require URL canonicalization and safe path handling eliminate the root cause of the weakness.
Enforcing strict access-control rules on canonical resource identifiers directly prevents authorization bypass via non-canonical URLs.