Apache Juneau: Cross-site request forgery via default-enabled content query-parameter body override
- 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? →
- 40/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
- Exploitation: none
- Automatable: yes
- Technical impact: total
Summary
Apache Juneau's REST server can be reached remotely, without logging in, through a cross-site request forgery flaw that lets an attacker deliver an attacker-chosen request body to endpoints, bypassing protections that rely on the HTTP method or content type instead of an anti-CSRF token. The flaw stems from a "content" query parameter that replaces the request body and is enabled by default on all HTTP methods.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
Cross-Site Request Forgery (CSRF) vulnerability in Apache Juneau.
The REST server accepts a "content" query parameter that replaces the request body, and this is enabled by default on every HTTP method, including GET. A cross-site link can therefore deliver an attacker-chosen request body to an endpoint without a CORS preflight, defeating protections that rely on the HTTP method or content type instead of an anti-CSRF token.
This issue affects Apache Juneau: through 9.2.0.
Users are recommended to upgrade to version 9.2.1, which fixes the issue. Applications that do not use the content parameter can also set disableContentParam to true.
cve.now Index
- Exploitation0/40No signal
- Exposure20/25No login or user action needed per the CVSS vector, CISA rates it automatable · Unknown: No advisory context yet
- Reach10/20Affects Maven packages
- Severity10/10CVSS 10.0, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 85 if added to CISA KEV
- Would score about 80 if CISA's SSVC rates exploitation active
- Would score about 45 if advisories confirm default setups are exposed
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
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: total
- Record last updated
Affected versions
- org.apache.juneau:juneau-rest-server.Maven
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-73099
Is CVE-2026-73099 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-73099?
org.apache.juneau:juneau-rest-server. (Maven): before 9.2.1.Source: cve.now feed data
How do I fix CVE-2026-73099?
Upgrade to a fixed version: 9.2.1.Source: cve.now feed data