CVE-2026-91858
MediumCVSS 6.5Summary
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.
Risk Assessment
An attacker can read files accessible to the Camel process and force network requests to chosen hosts, potentially leading to data leakage and SSRF.
Recommendation
Update Apache Camel to a version containing the fix, or remove the alternative JAXP TransformerFactory from the classpath if it is not required.
Other vulnerabilities in Apache Camel
See all- CVE-2026-88901High
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.
- CVE-2026-85317Medium
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.
- CVE-2026-85316Medium
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.
- CVE-2026-85315Medium
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.
- CVE-2026-85314Medium
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.
- CVE-2026-85313Medium
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.
- CVE-2026-85312Medium
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.
- CVE-2026-85301Medium
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.
- CVE-2026-85300Medium
An incorrect default permissions vulnerability exists in the Apache Camel PQC component. When writing generated key material to disk, the component used the process default umask rather than restricting the file to its owner, potentially allowing other local accounts to read the private key.
- CVE-2026-85296Medium
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.
Original NVD description (English source)
FopProducer transforms the incoming XSL-FO message body by creating a javax.xml.transform.TransformerFactory through TransformerFactory.newInstance() and enabling only FEATURE_SECURE_PROCESSING before running an identity transform over the body. On the JDK's built-in transformer, that feature alone already empties the accessExternalDTD and accessExternalStylesheet limits, so an external DTD or entity is refused. When a third-party JAXP TransformerFactory such as Saxon-HE is on the classpath, for example because the application also uses camel-xslt-saxon or camel-saxon, TransformerFactory.newInstance() returns that implementation instead, and FEATURE_SECURE_PROCESSING on its own does not restrict external resource access on it. A DOCTYPE with an external subset, or an external general entity, declared in the XSL-FO document is then resolved and expanded while the body is transformed. An external sender whose XSL-FO reaches a fop producer could therefore read files readable by the Camel process and cause the process to issue requests to hosts the document names. camel-fop does not bring such a factory itself, and excludes Xalan, so a default deployment using the JDK transformer is not affected; the issue is reachable only where another component has placed an alternative JAXP TransformerFactory on the classpath. Releases on the 4.14.x line and earlier reached end of life before this issue was resolved and do not receive a fix.
Vulnerability data from NVD (NIST) · CISA KEV · EPSS