← Übersicht Nicht im beobachteten Stack

Apache Camel: Camel-Platform-HTTP Request-Header Echo Suppression Bypassed by Header-Name Casing

CVE-2026-85254

Mittel · CVSS 6.5 Red Hat: Moderate Netzwerk · ohne Login Kein Fix bekannt

Veröffentlicht
19.10.2026 12:36
Zuletzt geändert
04.11.2026
EPSS (30 Tage)
0.7 %
CVSS-Vektor
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Beschreibung

Originaltext der Quelle, nicht übersetzt.

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.

Status beim Hersteller

Red Hat stuft seine Produktlinien ein: 4 betroffen.

OpenShift Serverless BetroffenFix zurückgestellt openshift-serverless-1/kn-eventing-integrations-aws-ddb-streams-source-rhel9, openshift-serverless-1/kn-eventing-integrations-aws-s3-sink-rhel9, openshift-serverless-1/kn-eventing-integrations-aws-s3-source-rhel9, openshift-serverless-1/kn-eventing-integrations-aws-sns-sink-rhel9, openshift-serverless-1/kn-eventing-integrations-aws-sqs-sink-rhel9, openshift-serverless-1/kn-eventing-integrations-aws-sqs-source-rhel9, openshift-serverless-1/kn-eventing-integrations-log-sink-rhel9, openshift-serverless-1/kn-eventing-integrations-timer-source-rhel9
Red Hat Fuse 7 Betroffenaußerhalb des Supports camel-platform-http
Red Hat build of Apache Camel 4 for Quarkus 3 BetroffenFix zurückgestellt camel-platform-http
Red Hat build of Apache Camel for Spring Boot 4 BetroffenFix zurückgestellt camel-platform-http
Weitere betroffene Pakete (2)
CVEApache Software Foundation/Apache Camel4.0.0 → 4.18.5, 4.19.0 → 4.22.1CVE-2026-85254
NVDapache:camel4.0.0 → 4.18.5, 4.19.0 → 4.22.1CVE-2026-85254

Empfohlene Prüfung

  1. Feststellen, ob und in welcher Version die betroffenen Pakete in Ihren Systemen, Images und Abhängigkeiten vorkommen.
  2. Wo eine Fix-Version genannt ist: aktualisieren. Wo nicht: Hersteller-Advisory und Referenzen auf Workarounds prüfen.
  3. Erreichbarkeit beachten: Der Angriffsweg (Netzwerk · ohne Login) ist aus dem CVSS-Vektor abgeleitet.

Diese Seite sagt nichts darüber, ob Ihre Systeme betroffen sind. Das klärt erst eine Prüfung Ihrer Versionen.