CVE-2026-85254
MEDIUMDescription
Improper Handling of Case Sensitivity vulnerability in Apache Camel Platform HTTP component. This issue affects Apache Camel: from 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1. The guard that prevents a request header being reflected into the response compared header names case sensitively, while HTTP header names are case insensitive. A caller could therefore defeat the suppression simply by varying the case of the header name. HTTP/2 makes the problem unconditional rather than optional: the protocol requires header names to be lowercase on the wire, so the comparison never matched and the suppression was inert for every request on an HTTP/2 connection. The consequence is that content the caller chose is echoed back in the response, which is the basis for response-splitting and cache-poisoning style attacks against whatever sits in front of the Camel endpoint. Upgrade to Apache Camel 4.23.0, which fixes the issue. Users on the 4.18.x LTS releases stream should upgrade to 4.18.5. Users on the 4.22.x LTS releases stream should upgrade to 4.22.1. Request header names are now compared case insensitively, so the suppression holds regardless of casing and works under HTTP/2. For deployments that cannot 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.
How to fix
TridentStack Control can deploy fixes like this automatically across your Windows, macOS, and Linux fleet. See how it works
Remediation is compiled from vendor and distribution security advisories. Always confirm against the linked source for your exact version and platform.
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
Exploit Intelligence
Moderate risk: more likely to be exploited than 53% of all known CVEs.
References
Related Vulnerabilities
Other CWE-178 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2025-27636 | Medium | 5.6 | 97% | - | Fix |
| CVE-2021-24347 | High | 8.8 | 54% | - | Fix |
| CVE-2020-12812 | Critical | 9.8 | 45% | KEV + Ransom | Fix |
| CVE-2003-0411 | High | 7.5 | 25% | - | - |
| CVE-2026-47323 | Critical | 9.8 | 20% | - | Fix |
| CVE-2018-9845 | Critical | 9.8 | 13% | - | Fix |
Common questions
How do I fix CVE-2026-85254?
Upgrade camel to 4.18.5 or later.
Is CVE-2026-85254 being actively exploited?
Not that we know of. CVE-2026-85254 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.68% is the estimated probability that it will be exploited in the next 30 days. That is higher than 53% of all scored CVEs.
How severe is CVE-2026-85254?
CVE-2026-85254 has a CVSS v3 base score of 6.5, rated medium. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
What does CVE-2026-85254 affect?
Published advisories record a fix for camel (NVD). Only products with a sourced advisory are listed, so treat this as what we can cite rather than a complete inventory.
Embed a live status badge for CVE-2026-85254
Markdown
[](https://tridentstack.com/cve/CVE-2026-85254)HTML
<a href="https://tridentstack.com/cve/CVE-2026-85254"><img src="https://tridentstack.com/cve/badge/CVE-2026-85254.svg" alt="CVE-2026-85254"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-11-03.