CVE-2026-85313 json
Apache Camel: Camel-Jetty Cross-Origin Credential Exposure via Allow-All CrossOriginFilter Defaults When enableCORS Is Set
published 2026-10-19 21 d ago modified 2026-11-03 5 d ago also EUVD-2026-104201
- cvss
- 4.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 35%
- public exploits
- 0
- none known
Summary
Permissive Cross-domain Policy with Untrusted Domains vulnerability in Apache Camel Jetty component.
This issue affects Apache Camel: from 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1.
Setting enableCORS on a Jetty endpoint installed Jetty's CrossOriginFilter with its stock defaults, which accept every origin and allow credentials. An operator asking for CORS therefore obtained a policy that lets a page on any origin make credentialed cross-origin requests to the endpoint and read the responses, without any indication that turning the option on had chosen an allow-all policy rather than an empty one to be filled in. This is the same defect class as the platform-http-vertx advisory published alongside it, in a different component.
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. enableCORS no longer grants credentials to an origin the operator did not name. A deployment that relied on any origin being accepted must now list its origins explicitly. For deployments that cannot upgrade immediately, configure the CrossOriginFilter parameters explicitly rather than relying on what enableCORS installs, naming the allowed origins.
Patch / fix
- Apache Software Foundation Apache Camel 4.18.5, 4.22.1, 4.23.0
- github.com/apache/camel#25829 pull request
- github.com/apache/camel#25937 pull request
- github.com/apache/camel#25938 pull request
- camel.apache.org/security/CVE-2026-85313.html advisory
- issues.apache.org/jira/browse/CAMEL-24450 advisory
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-85313 updated cvss 4.3
org.apache.camel/camel-jetty: Apache Camel Jetty: Information disclosure via overly permissive CORS configuration
-
Red Hat Fuse 7 camel-jetty 2.23.2.fuse-7_11_1-00015-redhat-00002affected: no fix planned “Out of support scope”
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 21 d ago
Exploit prediction
0.41% chance of exploitation in the next 30 days, higher than 35% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N |
Affected products
- Apache Software Foundation Apache Camel
Classification
- Weakness
-
- CWE-942 Permissive Cross-domain Security Policy with Untrusted Domains
References
-
github.com
/apache/camel/pull/25829
patch, issue-tracking
-
github.com
/apache/camel/pull/25937
patch, issue-tracking
-
github.com
/apache/camel/pull/25938
patch, issue-tracking
-
camel.apache.org
/security/CVE-2026-85313.html
vendor-advisory, mitigation, patch
-
issues.apache.org
/jira/browse/CAMEL-24450
issue-tracking, patch, vendor-advisory
Sources
- CVE List CVE-2026-85313
- NVD CVE-2026-85313
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.