Quick answers
- Is CVE-2026-73099 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-73099 being exploited in the wild.
- How severe is CVE-2026-73099?
- Informational severity, published 5 November 2026.
- Which products and versions are affected?
- Apache Juneau through 9.2.0.
- Is there a fix for CVE-2026-73099?
- Yes: fixed in 9.2.1. Until then: Set the disableContentParam configuration option to true if the application does not require the content query parameter feature. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-73099 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-73099?
- Check whether you run Apache Juneau at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 9.2.1
Set the disableContentParam configuration option to true if the application does not require the content query parameter feature.
Technical details
The vulnerability is a cross-site request forgery (CSRF) bypass in Apache Juneau's REST server where the "content" query parameter accepts and processes attacker-supplied request bodies on all HTTP methods including safe methods like GET, defeating standard CSRF protections that rely on HTTP method or content-type validation. An unauthenticated attacker can craft a cross-site link that delivers a malicious request body to vulnerable endpoints without triggering CORS preflight requirements. The issue affects versions through 9.2.0 and is fixed in 9.2.1.
Affected products
- Apache Juneau through 9.2.0
Timeline
- 2026-11-05: disclosed