Apache Juneau
CVE-2026-121489
MEDIUM
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach exposed DirectoryResource with a file flag enabled
-
ExploitCraft request path with ../ traversal segments
-
ExecutionResource resolves path outside configured root
-
ImpactRead, delete, or write files beyond root
Vulnerability Assessment
| Exploitation Conditions | Exploitation requires that the application expose the Juneau microservice DirectoryResource (juneau-microservice-core) to untrusted clients AND that at least one of allowViews, allowDeletes, or allowUploads be explicitly enabled - all three are off by default, so default deployments are not affected. Given those prerequisites, an unauthenticated client can exploit it by sending a request path containing parent-directory (../) segments; no user interaction or credentials are needed. The limiting factors are therefore the non-default configuration and whether the resource is reachable, and the achievable impact (read vs. delete vs. write) is bounded by which specific flag(s) the operator enabled and by the server process's filesystem permissions. |
| Impact | No CVSS vector, EPSS score, KEV entry, or PoC reference is provided for CVE-2026-121489, and vuln.today's decision label is 'awaiting_data', so this assessment rests on the Apache advisory text alone. The vendor rates it 'moderate', and the decisive mitigating factor stated by the advisory is that the enabling settings (allowViews, allowDeletes, allowUploads) are OFF by default - only applications that deliberately expose a Juneau microservice DirectoryResource with one of these flags enabled are exploitable, which sharply narrows the real-world population. Where it IS exploitable, the mechanism (path building from the request path without verifying the result stays under the configured root) is a classic directory traversal that an unauthenticated client can trigger, and impact can escalate from file disclosure to arbitrary deletion or write depending on which flags are set. There is no evidence of active exploitation and no public exploit was identified at time of analysis; combined with the off-by-default requirement and Juneau's modest deployment footprint, this is a real but conditional issue rather than a widespread emergency. Exploitation status, EPSS, and any PoC are MISSING from the input and should be treated as unknown, not as zero. |
| Exploit ScenarioDerived | An application exposes a Juneau microservice DirectoryResource to the network with allowViews (or allowDeletes/allowUploads) enabled. An unauthenticated attacker sends a request whose path contains parent-directory (../) segments; because the resource does not confine the resolved path to the configured root, the server reads, deletes, or writes a file outside that root wherever the process has filesystem access. No public exploit was identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Nov 03, 2026
Path traversal in Apache Juneau's microservice DirectoryResource (juneau-microservice-core and juneau-commons through 9.2.0) lets an unauthenticated remote client use parent-directory segments in the request path to read, delete or write files outside the configured root directory, anywhere the server process has filesystem access. Exploitation is gated on non-default configuration: the resource must be reachable by untrusted clients and at least one of allowViews, allowDeletes or allowUploads must be explicitly enabled - all three are off by default, so default deployments are unaffected - and the achievable impact is bounded by which flag is enabled and by the server process's permissions. Apache fixed the issue in Juneau 9.2.1 by resolving each path against the root directory and returning 403 Forbidden for any path that escapes it; no public exploit code was identified at time of analysis (no KEV entry, no EPSS score and no PoC reference provided, decision label awaiting_data).
RemediationAI
Vendor-released patch: 9.2.1. Upgrade all org.apache.juneau artifacts - including juneau-microservice-core, juneau-commons and the juneau-shaded-* and other aggregate artifacts that embed them - to version 9.2.1 (Maven org.apache.juneau, version 9.2.1; binaries at https://downloads.apache.org/juneau/9.2.1/). CVE-2026-121489 is one of several issues fixed in that release, which also changes some defaults: request bodies over 1 MB now require a larger @Rest(maxInput), error responses no longer carry internal exception detail unless renderResponseStackTraces is enabled, and the content query parameter is only honored on PUT and POST - validate applications against these behavior changes before rolling out. If upgrading immediately is not possible, the advisory's mitigation is to disable allowViews, allowUploads and allowDeletes on DirectoryResource (the resource then cannot serve, delete or accept files at all, with the trade-off that its file-serving functionality is lost), or to avoid exposing DirectoryResource to untrusted clients at all; no other workaround is described by the vendor. Advisory and download references: https://seclists.org/oss-sec/2026/q4/482, https://downloads.apache.org/juneau/9.2.1/, https://juneau.apache.org/security.
Affected ProductsAI
Apache Juneau through 9.2.0 is affected, specifically the Maven artifacts org.apache.juneau:juneau-microservice-core and org.apache.juneau:juneau-commons up to and including version 9.2.0. The advisory states that the juneau-shaded-* and other aggregate artifacts embed the affected modules and are affected in the same way, so they must be upgraded to 9.2.1 as well. Exposure additionally requires that DirectoryResource be exposed to untrusted clients with at least one of allowViews, allowDeletes or allowUploads enabled, since all three default to off. Fixed builds are published as org.apache.juneau version 9.2.1 (released 2026-11-03) at https://downloads.apache.org/juneau/9.2.1/; the advisory text is at https://seclists.org/oss-sec/2026/q4/482 and the project security page at https://juneau.apache.org/security.
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Apache Juneau is an Apache Java toolkit whose juneau-marshall module provides serializers and parsers and whose juneau-rest-server / juneau-microservice-core modules provide REST and microservice plumbing. DirectoryResource is a microservice resource that maps request paths onto files under a configured root directory. In the affected versions the resource builds the target file path directly from the request path without verifying that the normalized result remains inside that root, so '..' segments supplied by the client can traverse to sibling and ancestor directories. What the client can then do depends entirely on the resource's per-operation switches: allowViews (read), allowDeletes (delete) and allowUploads (write), all of which default to off, which is why the advisory rates the issue moderate and why only applications that explicitly enabled them are exposed. The 9.2.1 fix canonicalizes the resolved path against the root and rejects escapes with HTTP 403. The flaw class is path traversal; no CWE identifier is recorded in the available data. Note that the affected modules are also embedded in the juneau-shaded-* and other aggregate artifacts, which inherit the same behavior and must be upgraded in lockstep.
Know when Java gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
Unauthenticated network traversal (PR:N, AV:N, AC:L); escaping the configured root changes scope (S:C); C/I/A:H reflects the worst case where allowViews, allowDeletes and allowUploads are enabled.
Description PRE-NVD
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
Attack Technique
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
Cross-Site Request Forgery exploits the automatic credential inclusion behavior of web browsers.
Path traversal exploits occur when applications use user-controlled input to construct file system paths without proper validation.
Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.
Oracle Java SE 7 Update 6 and earlier contains multiple sandbox bypass vulnerabilities via the ClassFinder and forName m
Remote code execution in IBM Sterling B2B Integrator, Sterling Integrator, and Tivoli Common Reporting allows unauthenti
Java Runtime Environment sandbox bypass via incorrect image channel verification in 2D component allows remote unauthent
Oracle Java SE JDK/JRE 7 and 6 Update 27 and earlier allows remote code execution with complete system compromise throug
JBoss Seam 2 in Red Hat JBoss EAP 4.3.0 fails to sanitize JBoss Expression Language inputs, allowing remote attackers to
Unspecified vulnerability in the Java Runtime Environment (JRE) component in Oracle Java SE 7 update 4 and earlier, 6 up
Multiple vulnerabilities in Oracle Java 7 before Update 11 allow remote attackers to execute arbitrary code by (1) using
Unspecified vulnerability in the Java Runtime Environment (JRE) component in Oracle Java SE 7 Update 2 and earlier, 6 Up
The WLS Security component in Oracle WebLogic Server 10.3.6.0, 12.1.2.0, 12.1.3.0, and 12.2.1.0 allows remote attackers
Unspecified vulnerability in the Java Runtime Environment (JRE) component in Oracle Java SE 7 Update 7 and earlier allow
Remote unauthenticated attackers can execute arbitrary code on Adobe ColdFusion servers through Java deserialization fla
The ExceptionDelegator component in Apache Struts before 2.2.3.1 interprets parameter values as OGNL expressions during
CVE.org
GitHub PoC
Exploit-DB