CVE-2026-121489 · Package
NO FIX YET · SEE WHAT TO DO
Apache Juneau's DirectoryResource microservice does not keep request paths inside its configured root directory. When view, upload or delete settings are enabled, a client can read, write or delete any file the server process can access.
first public Nov 5, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Applications built on Apache Juneau that expose the DirectoryResource microservice with its view, upload or delete settings turned on, which are off by default. Applications that do not use DirectoryResource, or keep those settings off, are not exposed by this description. The sources do not say whether the flaw is reachable without authentication.
Not affected if default-config, resource-not-used
Who cares apache-juneau, java, microservice
9.2.0.DirectoryResource and check whether its view, upload or delete settings are enabled.9.2.1.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.
This page as .md · .json · 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.