CVE-2026-8384
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn 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 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceEclipse Jetty contains a path normalization flaw where certain URI patterns with semicolons (e.g., `/public;/../admin/secret.txt`) result in an unresolved path containing `..` sequences (`/public/../admin/secret.txt`) instead of the properly resolved path (`/admin/secret.txt`). While Jetty's own file serving is protected by alias checking, web applications that rely on Jetty to provide resolved paths may receive unexpected unresolved paths, potentially leading to security misunderstandings or logic errors.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 12.0.0, < 12.0.35>= 12.1.0, < 12.1.9CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed Jetty versionLocate the jetty-version.jar or jetty-core jar in your deployment, or check the pom.xml dependency for org.eclipse.jetty:jetty-server. Run: java -jar jetty-version.jar or inspect META-INF/MANIFEST.MF in the jetty-core jarAffected if The version number is >= 12.0.0 and < 12.0.35, or >= 12.1.0 and < 12.1.9
-
Verify Jetty is being used as the HTTP serverConfirm your application runs on Eclipse Jetty 12.x by checking how the server is started (e.g., org.eclipse.jetty.server.Server in code, or --module=server in jetty/start.d configuration)Affected if Your application explicitly uses Jetty 12.x as the HTTP server container
-
Check for path-handling code relying on Jetty resolutionSearch your codebase for uses of HttpServletRequest methods that return paths: getPathInfo(), getRequestURI(), getRequestURL(), getPathTranslated(), or org.eclipse.jetty.server.Request.getHttpURI().getPath()Affected if Your application code uses these methods to obtain paths that are then used for security decisions, file access, or business logic without additional canonicalization
-
Identify semicolon URI pattern usageReview application code or reverse proxy logs for URIs containing semicolons (e.g., /path;/extra or /public;/../admin). Search for patterns like \; in regex or examine incoming request pathsAffected if Your application processes or logs URIs with semicolons that could trigger the normalization issue
-
Confirm absence of path canonicalization in your codeSearch your codebase for path normalization routines: java.io.File.getCanonicalPath(), java.nio.file.Path.normalize(), or similar canonicalization logic applied to paths obtained from Jetty request methodsAffected if Your application does NOT perform its own canonicalization on paths retrieved from Jetty before using them in security-sensitive operations
You are affected if you run Jetty 12.0.0-12.0.34 or 12.1.0-12.1.8 AND your application relies on Jetty-provided paths (getPathInfo, getRequestURI) containing semicolons without performing its own path canonicalization.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped12.0.3512.1.9
Web applications using Jetty should implement their own path validation and canonicalization before using paths returned by Jetty, regardless of what Jetty provides. Monitor for Jetty security updates addressing this path normalization issue.
Jetty 12.0.35 or later for 12.0.x branch; Jetty 12.1.9 or later for 12.1.x branch
- Identify the Jetty 12.x branch in use (12.0.x or 12.1.x)
- If using Jetty 12.0.x, upgrade to version 12.0.35 or later
- If using Jetty 12.1.x, upgrade to version 12.1.9 or later
- Restart the Jetty server after upgrading
- Verify the fix by testing that URI paths with semicolons (like /public;/../) are properly resolved to the canonical path
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-8384 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-8384 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data