CVE Catalog

CVE-2026-84176

MediumCVSS 6.5
Published: Updated: Translated: NVD NIST

Exploitation Probability (EPSS)

Low risk
0.44%

37th percentile - higher than 37% of all known CVEs

Summary

A vulnerability in the Apache Camel Platform HTTP Vertx component involves improper CORS handling: the Access-Control-Allow-Credentials: true header is sent regardless of the origin check result, and when camel.server.cors.origins is unset the handler reflects any origin in Access-Control-Allow-Origin. As a result, any page can make credentialed cross-origin requests to the Camel endpoint and read the responses.

Risk Assessment

This may allow an attacker from any website to read data from Camel endpoints in the context of a logged-in user, leading to information disclosure or actions performed on the victim's behalf.

Recommendation

Upgrade Apache Camel to 4.23.0 (or 4.18.5 / 4.22.1 for the LTS streams). If an immediate upgrade is not possible, explicitly set camel.server.cors.origins to the list of allowed origins instead of leaving it unset.

Other vulnerabilities in Apache Camel

See all
Original NVD description (English source)

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.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS