# CVE-2026-121489: Apache Juneau: Path traversal in DirectoryResource allows reading files outside the configured root directory


- **Severity:** Critical 10.0 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 5 Nov 2026
- **Updated:** 10 Nov 2026
- **Also known as:** GHSA-6jw3-6826-3jf9

## What is CVE-2026-121489?

CVE-2026-121489 is a critical vulnerability in Apache Juneau, published on 5 Nov 2026. 

### Official description

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in Apache Juneau.

The microservice DirectoryResource does not keep request paths inside its configured root directory. When an application enables the resource's view, upload or delete settings (all off by default), a client can read, write or delete files outside the root, anywhere the server process has access.

This issue affects Apache Juneau: through 9.2.0.

Users are recommended to upgrade to version 9.2.1, which fixes the issue.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

No fix has been published for CVE-2026-121489 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-121489 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-121489 is a critical vulnerability in Apache Juneau, published on 5 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-121489 in the wild and no public exploit code.

Affected product: Apache Juneau. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-121489/ (Markdown: https://insights.sbomify.com/CVE-2026-121489/index.md)
```

## Sources

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

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