CVE-2026-85313
MEDIUMDescription
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.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
Exploit Intelligence
Low risk: more likely to be exploited than 19% of all known CVEs.
References
Related Vulnerabilities
Other CWE-942 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2026-22812 | High | 8.8 | 17% | - | Fix |
| CVE-2026-59726 | Critical | 10.0 | 3.0% | - | - |
| CVE-2023-38122 | High | 7.2 | 1.9% | - | Fix |
| CVE-2026-84452 | High | 8.6 | 1.6% | - | - |
| CVE-2026-61736 | Critical | 9.3 | 1.4% | - | - |
| CVE-2023-38125 | High | 8.8 | 1.3% | - | Fix |
Common questions
How do I fix CVE-2026-85313?
No published fix for CVE-2026-85313 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-85313 being actively exploited?
Not that we know of. CVE-2026-85313 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.27% is the estimated probability that it will be exploited in the next 30 days. That is higher than 19% of all scored CVEs.
How severe is CVE-2026-85313?
CVE-2026-85313 has a CVSS v3 base score of 4.3, rated medium. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-85313
Markdown
[](https://tridentstack.com/cve/CVE-2026-85313)HTML
<a href="https://tridentstack.com/cve/CVE-2026-85313"><img src="https://tridentstack.com/cve/badge/CVE-2026-85313.svg" alt="CVE-2026-85313"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-10-19.