# CVE-2026-8384: Eclipse Jetty: Path parameter traversal

> Attackers can bypass path resolution checks in Jetty, potentially allowing web applications to access restricted files if they trust the provided path.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 Jul 2026
- **Updated:** 14 Jul 2026
- **Also known as:** CLEANSTART-2026-BC80499, CLEANSTART-2026-DT46097, CLEANSTART-2026-HR51503, CLEANSTART-2026-JC61209, CLEANSTART-2026-KE92927, CLEANSTART-2026-ZO93584, DEBIAN-CVE-2026-8384, ECHO-477e-dee8-c56b, GHSA-w7x5-g22v-xqhr, MINI-242h-c32r-cqc6, MINI-2j4j-f8cp-hq2q, MINI-3f3x-mrv3-pw83, MINI-3pp6-739q-3qv5, MINI-3v5j-3j8h-534h, MINI-48hg-5pcg-cxj7, MINI-5974-mx95-vm62, MINI-6623-7rhh-mpm2, MINI-75wx-62h3-vqpm, MINI-7chh-rxfm-538w, MINI-7jhf-x69f-7gph, MINI-7r8p-9q7w-2pxg, MINI-7x8f-886f-26j5, MINI-835j-5r48-c45m, MINI-853g-c6ww-7mr5, MINI-88jq-r9pg-c69p, MINI-898m-xwj3-qc28, MINI-9vjp-45jw-px5v, MINI-c5fp-rg9j-h6qw, MINI-f234-39qh-q64w, MINI-fg8f-c8pj-3vcc, MINI-gfvm-qg5v-pgrx, MINI-j64q-vj5f-pxrf, MINI-j7h2-f634-h2q2, MINI-jvg3-hg59-m536, MINI-jw66-r6hp-w77g, MINI-m86x-hf32-25f2, MINI-mc4w-xm4p-46gw, MINI-mjf4-gg85-74pq, MINI-p6f3-7x4g-h9x2, MINI-pcjj-4gjp-c5w4, MINI-qpc7-9w62-8459, MINI-r4r8-wxpv-v22v, MINI-rprj-f27j-ffx6, MINI-rwh6-5c78-8933, MINI-v2rw-r7p6-vrjr, MINI-v42r-4296-g2hq, MINI-v74j-m3jv-wxjq, MINI-v8w6-cwm2-f4f2, MINI-vcf8-638w-82fm, MINI-vcp6-9q5m-7qv8, MINI-vrg5-qqh9-4gc7, MINI-vvq7-vmpg-4c8c, MINI-wv42-jcpx-266v, UBUNTU-CVE-2026-8384

## What is CVE-2026-8384?

CVE-2026-8384 is a medium-severity path traversal vulnerability in Eclipse Jetty, published on 14 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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 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.

Weakness: CWE-647 (Use of Non-Canonical URL Paths for Authorization Decisions)

## Which versions are affected by CVE-2026-8384?

4 open source packages ship an affected version, including org.eclipse.jetty:jetty-util. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.eclipse.jetty:jetty-util` | Maven | From 12.0.0 | 12.0.35 |
| `org.eclipse.jetty:jetty-util` | Maven | From 12.0.0 | 12.0.35 |
| `org.eclipse.jetty:jetty-util` | Maven | From 12.1.0 | 12.1.9 |
| `org.eclipse.jetty:jetty-util` | Maven | From 12.1.0 | 12.1.9 |

Products: Eclipse Jetty.

## How do I fix CVE-2026-8384?

Upgrade org.eclipse.jetty:jetty-util to a fixed version for your release line: 12.0.35 or 12.1.9.

## Is CVE-2026-8384 being exploited?

There is no known exploitation of CVE-2026-8384 in the wild and no public exploit code.

## Other vulnerabilities in Eclipse Jetty

- [CVE-2016-4800](https://insights.sbomify.com/CVE-2016-4800/): Jetty contains an alias issue that could allow unauthenticated remote code execution due to specially crafted request (critical 9.8)
- [CVE-2019-17638](https://insights.sbomify.com/CVE-2019-17638/): Operation on a Resource after Expiration or Release in Jetty Server (critical 9.4)
- [CVE-2018-12538](https://insights.sbomify.com/CVE-2018-12538/): Access and integrity issue within Eclipse Jetty (high 8.8)
- [CVE-2026-10050](https://insights.sbomify.com/CVE-2026-10050/): Digest authentication lossy encoding (high 8.7)
- [CVE-2025-5115](https://insights.sbomify.com/CVE-2025-5115/): MadeYouReset HTTP/2 vulnerability (high 7.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-8384 and fix it if it is affected.

What it is: CVE-2026-8384 is a medium-severity path traversal vulnerability in Eclipse Jetty, published on 14 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-8384 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.eclipse.jetty:jetty-util (Maven): affected from 12.0.0; fixed in 12.0.35
- org.eclipse.jetty:jetty-util (Maven): affected from 12.0.0; fixed in 12.0.35
- org.eclipse.jetty:jetty-util (Maven): affected from 12.1.0; fixed in 12.1.9
- org.eclipse.jetty:jetty-util (Maven): affected from 12.1.0; fixed in 12.1.9

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-8384/ (Markdown: https://insights.sbomify.com/CVE-2026-8384/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-8384
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-8384
- OSV: https://osv.dev/vulnerability/CVE-2026-8384

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-8384/
Summaries are generated and may contain mistakes; the official description above is the record.