Live › vulnerability › CVE-2026-85313
Go to dashboardTurning on enableCORS for a Jetty endpoint in Apache Camel installs a CORS filter that accepts every origin and allows credentials. A web page on any other site can then make credentialed requests to the endpoint and read the responses.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Teams running Apache Camel 4.0.0 up to 4.18.5 or 4.19.0 up to 4.22.1 that expose a Jetty endpoint with enableCORS set. The exposure depends on the endpoint being reachable from browsers on other origins and on it returning data that a credentialed request could read. Teams that do not use the Camel Jetty component, or that never set enableCORS, can skip it.
No product ranges from the sources yet.
enableCORS on Jetty endpoints.mvn dependency:tree | grep camel-jetty or the Camel version in the build file, and compare it against 4.18.5 and 4.22.1.4.23.0.4.18.5; on the 4.22.x LTS stream, upgrade to 4.22.1.enableCORS.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-85313")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.