CVE-2026-85300

FopProducer transforms the incoming XSL-FO body by creating a TransformerFactory via TransformerFactory.newInstance() and enabling only FEATURE_SECURE_PROCESSING. When a third-party JAXP TransformerFactory such as Saxon-HE is on the classpath, that feature alone does not restrict external resource access, so an external DTD or entity declared in the XSL-FO document is resolved and expanded. An external sender can therefore read files readable by the Camel process and cause it to issue requests to hosts the document names.

Improper Restriction of XML External Entity Reference (XXE) vulnerability in the Smooks component (camel-smooks) of Apache Camel. The default Woodstox SAX parser resolves external entities and loads external DTDs, allowing an attacker to read local files or issue requests to internal network locations via the XML body. Affects versions from 4.7.0 before 4.18.5 and from 4.19.0 before 4.22.1.

A use of cache containing sensitive information vulnerability exists in the Apache Camel HTTP component. The JVM-global OAuth2 token cache key omitted the requested scope, resource indicator and token endpoint, so two endpoints differing only in those fields shared a cache entry and an endpoint could be served a token minted for a different scope, resource or authorization server.

An insufficient granularity of access control vulnerability exists in the Apache Camel Platform HTTP component. The component decided proxy mode by testing whether the configured path started with the string "proxy" rather than matching exactly, so endpoints such as proxyStatus or proxy-config became proxies without the route author's intent and forwarded requests onward.

A generation of error message containing sensitive information vulnerability exists in the Apache Camel gRPC component. When a route behind a gRPC consumer failed, the exception message was placed into the gRPC status description, which is transmitted to the calling client, so an external caller could read internal error messages including class and package names, paths, host names and connection details.

An improper input validation vulnerability exists in the Apache Camel Mail component. The MimeMultipart data format retained an unfiltered path where unmarshalling a multipart message mapped mail.smtp headers onto the Exchange with no filter applied, so an external sender could set them and influence how a downstream mail producer connects and sends.

A permissive cross-domain policy with untrusted domains vulnerability exists in the Apache Camel Jetty component. Setting enableCORS installed Jetty's CrossOriginFilter with stock defaults accepting every origin and allowing credentials, so a page on any origin could make credentialed cross-origin requests and read responses.

An improper input validation vulnerability exists in the Apache Camel Core component. The saga processor consulted a header named Long-Running-Action without a Camel prefix, so an external sender could supply it on an inbound message and name the saga the exchange joined, attaching their request to a long-running action started by someone else.

An improper authentication vulnerability exists in the Apache Camel Keycloak component. The security processor validated the token issuer only when the introspection response contained an iss claim; when absent, the check was skipped rather than treated as a failure, potentially allowing tokens from an unintended issuer to be accepted.

An exposure of data element to wrong session vulnerability exists in the Apache Camel AS2 component. Signing material for an individual request was stored in state shared across requests, so with multiple trading partners a Message Disposition Notification could be signed with another partner's key.