← Übersicht Nicht im beobachteten Stack

Apache Camel: Camel-Platform-HTTP-Vertx Cross-Origin Credential Exposure via Wildcard Origin Reflection

CVE-2026-84176

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

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

Beschreibung

Originaltext der Quelle, nicht übersetzt.

Permissive Cross-domain Policy with Untrusted Domains vulnerability in Apache Camel Platform HTTP Vertx component. This issue affects Apache Camel: from 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1. createCorsHandler() set Access-Control-Allow-Credentials: true outside the origin check, so the header went out on every response to a request carrying an Origin header, including responses to origins the handler had just decided not to allow. When camel.server.cors.origins is unset, the handler treats every origin as allowed and echoes the caller's own Origin back as Access-Control-Allow-Origin. Together those produce the credentialed any-origin configuration that the fetch specification refuses to express as a literal wildcard, which is precisely why reflecting the origin is the usual way around that rule. A page on any origin could therefore make credentialed cross-origin requests to the Camel endpoint and read the responses. 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. Access-Control-Allow-Credentials is now sent only when the request origin matched an origin the operator actually configured. With no origin list the origin is still reflected, as before, but credentials are not granted, and Vary: Origin is now set whenever the origin is reflected so that a shared cache cannot serve one origin's response to another. For deployments that cannot upgrade immediately, set camel.server.cors.origins to the explicit list of origins that need access rather than leaving it unset.

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-vertx
Red Hat build of Apache Camel 4 for Quarkus 3 BetroffenFix zurückgestellt camel-platform-http-vertx
Red Hat build of Apache Camel for Spring Boot 4 BetroffenFix zurückgestellt camel-platform-http-vertx
Weitere betroffene Pakete (2)
CVEApache Software Foundation/Apache Camel4.0.0 → 4.18.5, 4.19.0 → 4.22.1CVE-2026-84176
NVDapache:camel4.0.0 → 4.18.5, 4.19.0 → 4.22.1CVE-2026-84176

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 · Nutzerinteraktion) 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.