CVE-2026-73117

Read full 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().

CVSS 10.0 (CRITICAL)

Attention and evidence

HYPE SCORE

0.0/10

REALITY · THREAT PRIORITY

3.5–6.0/10

Missing inputs: range of priority

Evidence confidence: Insufficient evidence

Why this priority?

Technical severity: CVSS 10: +3.50

Fresh prediction unavailable

General review priority, not probability, victim count or asset-specific risk. A range covers missing CVSS/EPSS inputs within the current evidence state.

Sources: 1 documents and public datasets.

Hype components

Headline sample (25%)

0/100

Press, 30 days (60%)

0/100

Grounded branding (15%)

0/100

HYPE TOTAL0/100

Sources and documents

Latest Vulnerabilities

Technical advisory · 05 Nov 2026, 12:17 · CVE-2026-73117 - Apache Juneau: Response header CRLF injection and open redirect when applications set headers or redirect targets from request data

Score evolution

● Hype ● Reality

First record: hype 0.0 · reality 3.5 (2026-11-05 13:31). The curve appears once the score changes.

Public exploit evidence

Public exploit entries / repo candidates

Evidence context and dated references

Reality is general threat/review priority, combining observed exploitation, CVSS severity and fresh EPSS. Evidence confidence is separate. This is not calibrated risk, a victim count or an asset-specific assessment. A range reflects missing numeric inputs. Published 1 days ago. Exploitation evidence usually takes weeks to show up: a low reality score can mean there is no data yet, not that the flaw is mild.

Evidence in context

Confidence in exploitation evidence: Insufficient evidence
Priority basis: Exploitation in attacks unconfirmed; CVSS 10; fresh prediction unavailable
Attention, last 30 days: 0 distinct story titles; 0 press documents; 0 publisher domains.
Technical potential: network access, no prior privileges, no user interaction.
Observed activity: No exploitation observation is recorded.
Known scale: Not quantified.
Evidence confidence basis: Insufficient evidence

Score evaluated: 2026-11-05 13:31:39.358721+00:00 · EPSS snapshot: not available

Source event timeline

Published

05 Nov 2026, 11:54

Score calculated

05 Nov 2026, 13:31