Live › vulnerability › CVE-2026-85254
Go to dashboardThe Apache Camel Platform HTTP component was meant to stop request headers from being reflected into responses, but it compared header names case sensitively. Because HTTP header names are case insensitive, a caller can bypass the suppression by changing header name casing, and on HTTP/2 the suppression never applies at all.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Applications that run Apache Camel 4.0.0 through 4.18.4 or 4.19.0 through 4.22.0 with the Platform HTTP component and reflect request headers back to callers. Systems sitting behind a cache or proxy are the ones where the echoed content can cause response-splitting or cache-poisoning. Teams on Camel 4.23.0, 4.18.5 or 4.22.1 or later can skip it.
No product ranges from the sources yet.
camel-platform-http or camel-bom in pom.xml or build.gradle) and see whether it is below 4.18.5 on the 4.18.x line or below 4.22.1 on the 4.22.x line4.23.04.18.54.22.1Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-85254")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.