Skip to main content

CVE-2026-84176: CWE-942 Permissive Cross-domain Policy with Untrusted Domains in Apache Software Foundation Apache Camel

0
Medium
VulnerabilityCVE-2026-84176cvecve-2026-84176cwe-942
Published: 10/19/2026 (10/19/2026, 10:30:00 UTC)
Source: CVE Database V5
Vendor/Project: Apache Software Foundation
Product: Apache Camel

Description

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.

CVSS v3.1

Score 6.5medium

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

Affected software

Apache Software Foundation

Apache Camel

Affected versions
>=4.0.0 <4.18.5>=4.19.0 <4.22.1
Apache Software Foundation/org.apache.camel:camel-platform-http-vertx
pkg:maven/Apache Software Foundation/org.apache.camel:camel-platform-http-vertx
Affected versions
>=4.0.0 <4.18.5>=4.19.0 <4.22.1

Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 10/19/2026, 11:04:26 UTC

Technical Analysis

The vulnerability in Apache Camel Platform HTTP Vertx component (CVE-2026-84176) is due to the createCorsHandler() method setting the Access-Control-Allow-Credentials header to true on all responses with an Origin header, regardless of whether the origin is allowed. If camel.server.cors.origins is unset, the handler treats all origins as allowed and reflects the caller's Origin header, effectively allowing credentialed cross-origin requests from any origin. This creates a permissive cross-domain policy with untrusted domains, violating the fetch specification's rules against credentialed wildcard origins. The issue affects Apache Camel versions >=4.0.0 <4.18.5 and >=4.19.0 <4.22.1. The fix, introduced in versions 4.18.5, 4.22.1, and 4.23.0, restricts Access-Control-Allow-Credentials to responses where the origin matches a configured allowed origin. Additionally, the Vary: Origin header is set when reflecting origins to prevent shared cache issues. Users unable to upgrade immediately should explicitly configure allowed origins via camel.server.cors.origins.

Potential Impact

This vulnerability allows any web page from any origin to make credentialed cross-origin requests to the affected Apache Camel HTTP endpoint and read the responses, potentially exposing sensitive information. The issue does not affect integrity or availability but compromises confidentiality by enabling unauthorized data access through cross-origin resource sharing (CORS) misconfiguration.

Mitigation Recommendations

A fix is available in Apache Camel versions 4.18.5, 4.22.1, and 4.23.0. Users should upgrade to one of these versions to resolve the vulnerability. For users who cannot upgrade immediately, explicitly setting camel.server.cors.origins to a list of allowed origins will mitigate the risk by restricting credentialed cross-origin requests to trusted domains only.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
apache
Date Reserved
2026-09-01T09:24:51.254Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 6ad5f5a22cdf04f65643556d

Added to database: 10/19/2026, 10:49:06 UTC

Last enriched: 10/19/2026, 11:04:26 UTC

Last updated: 10/19/2026, 19:06:46 UTC

Views: 6

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses