Severity:
CVSS 3.1: 4.3 (medium) CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
Affected versions:
- Apache Camel (org.apache.camel:camel-jetty) 4.0.0 before 4.18.5
- Apache Camel (org.apache.camel:camel-jetty) 4.19.0 before 4.22.1
- Apache Camel (org.apache.camel:camel-jetty) 4.18.5 unaffected
- Apache Camel (org.apache.camel:camel-jetty) 4.22.1 unaffected
- Apache Camel (org.apache.camel:camel-jetty) 4.23.0 unaffected
Description:
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.
Solution:
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.
Work Arounds:
For deployments that cannot upgrade immediately, configure the
CrossOriginFilter parameters explicitly rather than relying on what enableCORS
installs, naming the allowed origins.
Credit:
Claude Security (finder)
Andrea Cosentino (remediation developer)
References:
https://camel.apache.org/security/CVE-2026-85313.html
https://issues.apache.org/jira/browse/CAMEL-24450
https://github.com/apache/camel/pull/25829
https://github.com/apache/camel/pull/25937
https://github.com/apache/camel/pull/25938
https://camel.apache.org/
https://www.cve.org/CVERecord?id=CVE-2026-85313
