Apache Juneau: Response header CRLF injection and open redirect when applications set headers or redirect targets from request data
- Exploited
- No known exploitation
- Fix
- Fixed in 9.2.1
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 9.2.1.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 37/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Apache Juneau's REST server does not check response header values or redirect targets, so an application that builds them from request data lets a remote attacker, without logging in, inject extra HTTP header lines or redirect users to an arbitrary external site. Exposure depends on application code that sets headers or redirect targets from request data.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Response Splitting') vulnerability in Apache Juneau.
The Apache Juneau REST server passed response header values and redirect targets to the servlet container unchecked. An application that sets a response header or redirect target from request data could let a remote client inject header lines (where the servlet container does not itself reject CR/LF) or redirect users to an arbitrary external site. The framework itself does not build headers or redirects from request data; exposure depends on application code.
This issue affects Apache Juneau: through 9.2.0.
Users are recommended to upgrade to version 9.2.1, which fixes the issue. Header values are now sanitized by default; applications that build redirect targets from request data must also switch from sendRedirect() to the new sendSafeRedirect().
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
- Reach10/20Affects Maven packages
- Severity10/10CVSS 10.0
- No patch0/5No signal
What would change the score
- Would score about 82 if added to CISA KEV
- Would score about 77 if CISA's SSVC rates exploitation active
- Would score about 42 if advisories confirm default setups are exposed
Impact
- Widely used
12 packages depend on org.apache.juneau:juneau-rest-server.Source: deps.dev
What to do
Upgrade to a fixed version: 9.2.1.
Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
Affected versions
- org.apache.juneau:juneau-rest-serverMaven
fixed in 9.2.1
Evidence 1
- Advisory
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-73117
Is CVE-2026-73117 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-73117?
org.apache.juneau:juneau-rest-server (Maven): before 9.2.1.Source: cve.now feed data
How do I fix CVE-2026-73117?
Upgrade to a fixed version: 9.2.1.Source: cve.now feed data