Quick answers
- Is CVE-2026-85254 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-85254 being exploited in the wild.
- How severe is CVE-2026-85254?
- Medium severity, with a CVSS score of 6.5, published 19 October 2026.
- Which products and versions are affected?
- Apache Camel 4.0.0 before 4.18.5, 4.19.0 before 4.22.1.
- Is there a fix for CVE-2026-85254?
- Yes: fixed in Apache Camel 4.18.5, 4.22.1, 4.23.0. Until then: For deployments unable to upgrade immediately, strip the headers in question in front of the Camel endpoint, or remove them from the response in the route rather than relying on the built-in suppression. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-85254 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-85254?
- Check whether you run Apache Camel 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: Apache Camel 4.18.5, 4.22.1, 4.23.0
For deployments unable to upgrade immediately, strip the headers in question in front of the Camel endpoint, or remove them from the response in the route rather than relying on the built-in suppression.
Technical details
The HTTP component in Apache Camel compares header names case-sensitively when deciding whether to suppress echoing them into responses, but HTTP header names are case-insensitive. HTTP/2 mandates lowercase header names on the wire, causing the suppression to fail entirely on HTTP/2 connections. An attacker can exploit this by submitting crafted headers with alternate casing (or via HTTP/2) to inject arbitrary content into response headers.
Affected products
- Apache Camel 4.0.0 before 4.18.5, 4.19.0 before 4.22.1
Timeline
- 2026-10-15: disclosed
- 2026-10-19: patched