Security
Apache Camel security information.
Read first
Security model and report scope
Before reporting, please read the Apache Camel Security Model.
It is the canonical reference the Apache Camel PMC uses when triaging security reports. It documents who is trusted, where the trust boundaries sit, which vulnerability classes are accepted as framework vulnerabilities, and which categories are out of scope — route-author or operator responsibility, explicit opt-ins, denial of service through unthrottled routes, third-party transitive CVEs not reachable through Camel code, management surfaces placed on an untrusted network, and automated-scanner output with no proof of concept. Reports that fall outside the documented scope are closed with a reference to that page.
The Camel subprojects — Camel Quarkus, Camel Spring Boot, Camel Karaf, Camel Kamelets, Camel Kafka Connector and Camel K — inherit the same trust model; report scope for them is governed by the same document unless a subproject publishes its own security model.
Software Bill of Materials (SBOM)
Every Camel release since 4.0.3 ships with PGP-signed CycloneDX SBOMs that list all dependencies, enabling supply chain risk analysis alongside the CVE advisories below. See Generating SBOMs for details.
Security Policy Enforcement
Camel includes built-in Security Policy Enforcement that validates security-sensitive configuration during startup and can prevent insecure configurations from reaching production.
See Security Policy Enforcement for configuration details.
Reporting new security problems with Apache Camel
The Apache Software Foundation takes a very active stance in eliminating security problems.
We strongly encourage folks to report such problems to the private security mailing list of the ASF Security Team, before disclosing them in a public forum.
Security advisories
| Reference | Affected | Fixed | Severity | Description |
|---|---|---|---|---|
| 2026 | ||||
| CVE-2026-91858 | From 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1. | 4.18.5, 4.22.1 and 4.23.0 | Medium | Camel-FOP: XML external entity processing - FopProducer created a TransformerFactory with only secure processing enabled, so when a third-party JAXP TransformerFactory such as Saxon-HE was on the classpath, an external DTD or entity declared in the XSL-FO input was resolved and expanded |
| CVE-2026-88901 | From 4.7.0 before 4.18.5, from 4.19.0 before 4.22.1. | 4.18.5, 4.22.1 and 4.23.0 | High | Camel-Smooks: XML external entity processing - the Smooks data format and component parsed the incoming XML message body with the reader Smooks resolves by default, which resolves external general and parameter entities and loads external DTDs, so an external entity declared in that body could read local files or reach internal hosts |
| CVE-2026-85317 | From 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1. | 4.18.5, 4.22.1 and 4.23.0 | Medium | Camel-HTTP: OAuth2 token confusion - the JVM-global token cache was keyed on fewer fields than shape the token, so an endpoint could be served a cached token minted for a different scope, resource or token endpoint |
| CVE-2026-85316 | From 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1. | 4.18.5, 4.22.1 and 4.23.0 | Medium | Camel-Platform-HTTP: unintended proxy mode - proxy mode was selected by testing whether the configured path started with proxy, so any path beginning with those characters silently became a proxy endpoint |
| CVE-2026-85315 | From 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1. | 4.18.5, 4.22.1 and 4.23.0 | Medium | Camel-gRPC: information disclosure - the route exception's message was placed into the gRPC status description, which is transmitted to the caller, so an internal error message reached an external client |
| CVE-2026-85314 | From 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1. | 4.18.5, 4.22.1 and 4.23.0 | Medium | Camel-Mail: header injection - the MimeMultipart data format mapped mail.smtp headers onto the Exchange without applying the filter, leaving open the path that CVE-2026-46584 was intended to close |
| CVE-2026-85313 | From 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1. | 4.18.5, 4.22.1 and 4.23.0 | Medium | Camel-Jetty: cross-origin credential exposure - setting enableCORS installed Jetty's CrossOriginFilter with its allow-all defaults, so every origin was accepted and credentials were granted to all of them |
| CVE-2026-85312 | From 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1. | 4.18.5, 4.22.1 and 4.23.0 | Medium | Camel-Core: saga hijacking - the saga processor consulted a Long-Running-Action header that sits outside the filtered Camel namespace, so an external sender could name the saga an exchange joined |
| CVE-2026-85301 | From 4.15.0 before 4.18.5, from 4.19.0 before 4.22.1. | 4.18.5, 4.22.1 and 4.23.0 | Medium | Camel-Keycloak: issuer validation bypass - the issuer check was skipped rather than failed when the token introspection response carried no iss claim, so a token from an unintended issuer could be accepted |
| CVE-2026-85300 | From 4.12.0 before 4.18.5, from 4.19.0 before 4.22.1. | 4.18.5, 4.22.1 and 4.23.0 | Medium | Camel-PQC: private key disclosure - generated key material was written to disk with the process default file permissions rather than restricted to the owner, so any local account able to read the directory could read the private key |
| CVE-2026-85296 | From 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1. | 4.18.5, 4.22.1 and 4.23.0 | Medium | Camel-AS2: cross-partner signing key confusion - per-request signing material was held in state shared across requests, so a receipt could be signed with the key belonging to a different trading partner |
| CVE-2026-85260 | From 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1. | 4.18.5, 4.22.1 and 4.23.0 | Medium | Camel-MLLP: protected health information disclosure - logPhi defaulted to true so HL7 payload content was written to the log out of the box, and two code paths logged it regardless of the setting |
| CVE-2026-85257 | From 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1. | 4.18.5, 4.22.1 and 4.23.0 | Medium | Camel-CXF: information disclosure - an exception thrown by the route was described back to the SOAP client in the fault, exposing internal exception types and messages that were never part of the service contract |
| CVE-2026-85254 | From 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1. | 4.18.5, 4.22.1 and 4.23.0 | Medium | Camel-Platform-HTTP: request-header echo suppression bypass - the check that stops a request header being echoed into the response compared header names case sensitively, so a differently cased name defeated it, and under HTTP/2 it never matched at all |
| CVE-2026-85251 | From 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1. | 4.18.5, 4.22.1 and 4.23.0 | High | Camel-HTTP: credential disclosure - with followRedirects enabled the Authorization header was re-attached to whatever host the Location header named, so the remote server chose which host received the credentials |
| CVE-2026-85250 | From 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1. | 4.18.5, 4.22.1 and 4.23.0 | High | Camel-XPath: XML external entity processing - the documentType=InputSource option handed the payload to an XPath engine that built its own parser with JDK defaults, so a DOCTYPE refused on the default document type was accepted and its external entity resolved |
| CVE-2026-85249 | From 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1. | 4.18.5, 4.22.1 and 4.23.0 | Medium | Camel-Tika: header injection - metadata parsed out of the submitted document was mapped onto the Exchange as headers without filtering, so the document could set headers the route relies on, such as CamelFileName |
| CVE-2026-85248 | From 4.12.0 before 4.18.5, from 4.19.0 before 4.22.1. | 4.18.5, 4.22.1 and 4.23.0 | Medium | Camel-PQC: signature verification bypass - one java.security.Signature instance was shared across concurrent exchanges without synchronization, so interleaved use could make a verification succeed for data it never covered |
| CVE-2026-85247 | From 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1. | 4.18.5, 4.22.1 and 4.23.0 | Medium | Camel-Knative: improper certificate validation - enabling SSL without configuring a truststore fell back to trusting every certificate, so turning TLS on was the thing that turned certificate validation off |
| CVE-2026-85246 | From 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1. | 4.18.5, 4.22.1 and 4.23.0 | Medium | Camel-Mina: information disclosure - the consumer wrote the route's exception straight back over the socket, handing the remote peer its class and message over a textline codec and its serialised form over the object codec |
| CVE-2026-85245 | From 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1. | 4.18.5, 4.22.1 and 4.23.0 | Medium | Camel-Thrift: cross-exchange data disclosure - unmarshalling deserialized into the shared defaultInstance rather than a copy, so fields set by one message remained visible to the next |
| CVE-2026-85243 | From 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1. | 4.18.5, 4.22.1 and 4.23.0 | Medium | Camel-Crypto-PGP: integrity verification downgrade - the modification detection code was verified only when the message used the integrity protected packet, so a sender choosing the legacy packet skipped the check entirely |
| CVE-2026-84181 | From 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1. | 4.18.5, 4.22.1 and 4.23.0 | Medium | Camel-Shiro: authentication bypass - the presented credentials were not verified when the Shiro subject already bound to the thread matched the incoming principal, so a request could reuse an authentication it never performed |
| CVE-2026-84180 | From 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1. | 4.18.5, 4.22.1 and 4.23.0 | Medium | Camel-Knative: information disclosure - a route failure was written back to the remote caller as the response body, so the exception class, message and stack trace of an internal error reached an external sender |
| CVE-2026-84178 | From 4.11.0 before 4.18.5, from 4.19.0 before 4.22.1. | 4.18.5, 4.22.1 and 4.23.0 | Medium | Camel-OAuth: login cross-site request forgery - the authorization code callback was not bound to the flow that started it, so a code obtained in any browser could be redeemed at the callback and bound to whichever session presented it |
| CVE-2026-84176 | From 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1. | 4.18.5, 4.22.1 and 4.23.0 | Medium | Camel-Platform-HTTP-Vertx: cross-origin credential exposure - Access-Control-Allow-Credentials was set outside the origin check and the caller's own Origin was reflected back when no origin list was configured, producing a credentialed any-origin CORS policy |
| CVE-2026-83531 | From 4.4.0 before 4.18.5, from 4.19.0 before 4.22.1. | 4.18.5, 4.22.1 and 4.23.0 | High | Camel-Dynamic-Router: The dynamic-router-control endpoint compiled the subscription predicate from an expression and an expression language supplied by the control message, allowing an actor who can send messages to a route that forwards them to the control endpoint to execute code in the Camel process |
| CVE-2026-80344 | From 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1. | 4.18.5, 4.22.1 and 4.23.0 | High | Camel-AS2: server-side request forgery and credential disclosure - the asynchronous MDN delivery address supplied by the remote partner was used as the destination for the receipt, so the sender chose where the Camel instance would connect and what credentials it would present |
| CVE-2026-80343 | From 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1. | 4.18.5, 4.22.1 and 4.23.0 | High | Camel-Netty-HTTP: security constraint bypass - the security constraint matched the request path case sensitively while dispatch to the route did not, so altering the case of a path segment skipped the constraint and still reached the endpoint |
| CVE-2026-80312 | From 4.11.0 before 4.18.5, from 4.19.0 before 4.22.1. | 4.18.5, 4.22.1 and 4.23.0 | High | Camel-OAuth: authentication bypass - the OAuth processors returned control to the route instead of stopping it when authentication could not be completed, so a request that failed authentication was processed as if it had succeeded |
| CVE-2026-79986 | From 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1. | 4.18.5, 4.22.1 and 4.23.0 | High | Camel-Azure-Files: the consumer built the remote path of a polled file from the name reported in the share listing without constraining it to the polled directory, so a crafted listing entry could be retrieved, deleted or renamed outside it |
| CVE-2026-79985 | From 4.2.0 before 4.18.5, from 4.19.0 before 4.22.1. | 4.18.5, 4.22.1 and 4.23.0 | High | Camel-SMB: the consumer built the remote path of a polled file from the name reported in the share listing without constraining it to the polled directory, so a crafted listing entry could be retrieved, deleted or renamed outside it |
| CVE-2026-79984 | From 4.18.0 before 4.18.5, from 4.19.0 before 4.22.1. | 4.18.5, 4.22.1 and 4.23.0 | High | Camel-Mina-SFTP: the consumer built the remote path of a polled file from the name reported in the server directory listing without constraining it to the polled directory, so a crafted listing entry could be retrieved, deleted or renamed outside it |
| CVE-2026-79983 | From 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1. | 4.18.5, 4.22.1 and 4.23.0 | High | Camel-FTP: the consumer built the remote path of a polled file from the name reported in the server directory listing without constraining it to the polled directory, so a crafted listing entry could be retrieved, deleted or renamed outside it |
| CVE-2026-78165 | From 2.11.0 before 4.18.5, from 4.19.0 before 4.22.1. | 4.18.5, 4.22.1 and 4.23.0 | High | Camel-Spring-Redis: The default JdkSerializationRedisSerializer deserializes Redis payloads with no ObjectInputFilter, allowing an actor who can publish to the subscribed channel to achieve remote code execution |
| CVE-2026-78164 | From 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1. | 4.18.5, 4.22.1 and 4.23.0 | High | Camel HTTP producers: property placeholders were resolved on the message-supplied endpoint-URI override headers, so an unauthenticated sender able to influence those headers could have configuration values and vault secrets expanded into the outbound request and no-argument registry bean methods invoked |
| CVE-2026-78163 | From 4.15.0 before 4.18.5, from 4.19.0 before 4.22.1. | 4.18.5, 4.22.1 and 4.23.0 | Medium | Camel-Docling: Unvalidated message body input source enables server-side request forgery and local file disclosure in DoclingProducer |
| CVE-2026-78162 | From 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1. | 4.18.5, 4.22.1 and 4.23.0 | Medium | Camel-Hazelcast: Incomplete fix for CVE-2026-43865 leaves managed instances without a Java deserialization filter, enabling remote code execution |
| CVE-2026-103413 | From 4.0.0 before 4.22.1. | 4.22.1 | High | Karavan applies unvalidated Kubernetes resources from a project's kubernetes.yaml |
| CVE-2026-103412 | From 3.18.0 before 4.22.1. | 4.22.1 | High | Karavan project file names escape the project directory when a project is committed to Git |
| CVE-2026-88789 | This issue affects Apache Camel Quarkus: from 3.2.0 before 3.33.3, from 3.34.0 before 3.40.0 | 3.33.3 and 3.40.0 | High | Camel Quarkus: Forced Xalan TransformerFactory drops upstream external-DTD/stylesheet hardening |
| CVE-2026-80354 | This issue affects Apache Camel K: from 2.0.0 before 2.9.3, from 2.10.0 before 2.10.2 | 2.9.3, 2.10.2 and 2.11.0 | Medium | Camel K Builder trait mavenProfiles ValueSources resolve tenant-named secrets in operator namespace |
| CVE-2026-80352 | This issue affects Apache Camel K: from 2.0.0 before 2.9.3, from 2.10.0 before 2.10.2 | 2.9.3, 2.10.2 and 2.11.0 | Critical | Camel K Master trait serviceAccountName YAML injection lets CR author apply arbitrary objects |
| CVE-2026-80351 | This issue affects Apache Camel K: from 2.0.0 before 2.9.3, from 2.10.0 before 2.10.2 | 2.9.3, 2.10.2 and 2.11.0 | Critical | Camel K Tenant repositories reach Maven execution inside operator pod |
| CVE-2026-78329 | From 4.11.0 before 4.14.9, from 4.15.0 before 4.18.4, from 4.19.0 before 4.22.0. | 4.14.9, 4.18.4 and 4.22.0 | Medium | Camel-Undertow: the endpoint discarded the undertow-specific header filter strategy in favour of the base HTTP one, so the undertow filtering never ran on endpoint-configured routes |
| CVE-2026-71300 | From 4.0.0 before 4.14.9, from 4.15.0 before 4.18.4, from 4.19.0 before 4.22.0. | 4.14.9, 4.18.4 and 4.22.0 | Medium | Camel-Atmosphere-Websocket: WebSocket dispatch header injection - the producer selected its target peers through Exchange headers whose names sat outside the filtered Camel namespace, so an external sender could take over the dispatch decision |
| CVE-2026-66908 | From 4.8.0 before 4.22.0. | 4.22.0 | High | Camel-platform-http-main: when JWT authentication was configured with a keystore but no issuer or audience, the iss and aud claims were never validated, so any unexpired token signed by a trusted key was accepted |
| CVE-2026-66907 | From 4.0.0 before 4.14.9, from 4.15.0 before 4.18.4, from 4.19.0 before 4.22.0. | 4.14.9, 4.18.4 and 4.22.0 | Medium | Camel-Google-Storage: the consumer appended the remote object name to the configured downloadFileName directory without constraining the result, so an object name containing traversal segments could write outside that directory |
| CVE-2026-66906 | From 4.0.0 before 4.14.9, from 4.15.0 before 4.18.4, from 4.19.0 before 4.22.0. | 4.14.9, 4.18.4 and 4.22.0 | Medium | Camel-Azure-Storage-Blob: the downloadBlobToFile operation built the local download target from the remote blob name without constraining it to the configured fileDir, so a name containing traversal segments could write outside that directory |
| CVE-2026-63621 | From 3.15.0 before 4.14.9, from 4.15.0 before 4.18.4, from 4.19.0 before 4.22.0. | 4.14.9, 4.18.4 and 4.22.0 | Medium | Camel-Knative: CloudEvent extension fields received in structured content mode were mapped onto message headers without applying any header filter strategy, so an untrusted sender could inject Camel-internal headers |
| CVE-2026-60093 | From 4.0.0 before 4.14.9, from 4.15.0 before 4.18.4, from 4.19.0 before 4.22.0. | 4.14.9, 4.18.4 and 4.22.0 | Medium | Camel-Azure-Storage-DataLake: the downloadToFile operation built the local download target from the remote path name without constraining it to the configured fileDir, so a name containing traversal segments could write outside that directory |
| CVE-2026-59230 | From 2.17.0 before 4.14.9, from 4.15.0 before 4.18.4, from 4.19.0 before 4.22.0. | 4.14.9, 4.18.4 and 4.22.0 | Medium | Camel-Mail: the MimeMultipart data format copied MIME headers onto the Camel message without a header filter strategy when unmarshalling with headersInline enabled, so a crafted message could inject Camel-internal headers |
| CVE-2026-43867 | From 4.18.0 before 4.18.3, from 4.19.0 before 4.21.0. | 4.18.3 and 4.21.0 | Medium | Camel-PQC: The AWS Secrets Manager key-lifecycle manager deserializes persisted key metadata with java.io.ObjectInputStream and no ObjectInputFilter (same defect as CVE-2026-46590, reported independently) |
| CVE-2026-43866 | From 3.0.0 before 4.14.8, from 4.15.0 before 4.18.3, from 4.19.0 before 4.21.0. | 4.14.8, 4.18.3 and 4.21.0 | High | Camel JMS deserialization filter bypass: a forged DefaultExchangeHolder carried in a JMS ObjectMessage passes the CVE-2026-40860 class check and is unmarshalled into the Exchange, letting an attacker who can publish an ObjectMessage inject the message body, headers, exchange properties, variables and exception |
| CVE-2026-56140 | From 4.0.0 before 4.14.8, from 4.15.0 before 4.18.3, from 4.19.0 before 4.21.0. | 4.14.8, 4.18.3 and 4.21.0 | Low | Camel-AWS2-SNS: An inbound Camel-namespace filter was added to Sns2HeaderFilterStrategy to align it with sibling components; because camel-aws2-sns is producer-only (no consumer) there is no reachable inbound header-injection path, so this is a defense-in-depth hardening change related to the camel-aws2-sqs issue CVE-2026-46456 |
| CVE-2026-56139 | From 4.0.0 before 4.14.8, from 4.15.0 before 4.18.3, from 4.19.0 before 4.21.0. | 4.14.8, 4.18.3 and 4.21.0 | Medium | Camel-Undertow: The muteException consumer option defaulted to false, so a processing error returned the full Java stack trace in the HTTP response body, disclosing sensitive internal information to unauthenticated clients - and the option was not honoured at all for Rest DSL consumers |
| CVE-2026-55994 | From 4.17.0 before 4.18.3, from 4.19.0 before 4.21.0. | 4.18.3 and 4.21.0 | High | Camel-Iggy: The inbound consumer maps externally-supplied Iggy message user-headers into the Exchange without a HeaderFilterStrategy, allowing injection of Camel control headers - enabling server-side request forgery and disclosure of secrets when bridged to an HTTP producer |
| CVE-2026-55993 | From 4.0.0 before 4.14.8, from 4.15.0 before 4.18.3, from 4.19.0 before 4.21.0. | 4.14.8, 4.18.3 and 4.21.0 | High | Camel-Atmosphere-Websocket: The inbound consumer maps externally-supplied WebSocket query parameters into the Exchange without a HeaderFilterStrategy, allowing injection of Camel control headers - enabling server-side request forgery and disclosure of secrets when bridged to an HTTP producer |
| CVE-2026-53913 | From 4.15.0 before 4.18.3, from 4.19.0 before 4.21.0. | 4.18.3 and 4.21.0 | High | Camel-Keycloak: KeycloakSecurityPolicy verifies the bearer access token only inside its role and permission checks, so in the default configuration (no required roles or permissions) the token is never verified and any non-null bearer value is accepted - a fail-open authentication bypass |
| CVE-2026-49365 | From 4.0.0 before 4.14.8, from 4.15.0 before 4.18.3, from 4.19.0 before 4.21.0. | 4.14.8, 4.18.3 and 4.21.0 | Medium | Camel-Netty-HTTP: The muteException consumer option defaulted to false, so a processing error returned the full Java stack trace in the HTTP response body, disclosing sensitive internal information to unauthenticated clients |
| CVE-2026-49099 | From 4.0.0 before 4.14.8, from 4.15.0 before 4.18.3, from 4.19.0 before 4.21.0. | 4.14.8, 4.18.3 and 4.21.0 | Medium | Camel-Salesforce: Non-Camel-prefixed Exchange header constants (sObjectQuery, sObjectSearch, apexUrl, ...) bypass the HTTP header filter, allowing an HTTP client to inject SOQL/SOSL queries, override the target SObject, and redirect Apex REST calls using the connected Salesforce user's permissions |
| CVE-2026-49098 | From 4.0.0 before 4.14.8, from 4.15.0 before 4.18.3, from 4.19.0 before 4.21.0. | 4.14.8, 4.18.3 and 4.21.0 | Medium | Camel-Kafka: The kafka.OVERRIDE_TOPIC (and other kafka.*) Exchange header constants used non-Camel-prefixed names that bypass the upstream HTTP header filter, allowing an HTTP client to redirect Kafka messages to an arbitrary topic |
| CVE-2026-49097 | From 4.0.0 before 4.14.8, from 4.15.0 before 4.18.3, from 4.19.0 before 4.21.0. | 4.14.8, 4.18.3 and 4.21.0 | Medium | Camel-IRC: The irc.sendTo (and other irc.*) Exchange header constants used non-Camel-prefixed names that bypass the HTTP header filter, allowing an HTTP client to redirect outgoing IRC messages to arbitrary channels or users |
| CVE-2026-49086 | From 4.12.0 before 4.14.8, from 4.15.0 before 4.18.3, from 4.19.0 before 4.21.0. | 4.14.8, 4.18.3 and 4.21.0 | Medium | Camel-Dapr: The Dapr Pub/Sub consumer copied the inbound CloudEvent's pub/sub-name and topic into producer-direction routing headers, allowing an actor who can publish to the subscribed topic to redirect the re-published message to an arbitrary Dapr Pub/Sub component and topic |
| CVE-2026-49042 | From 4.8.0 before 4.18.3, from 4.19.0 before 4.21.0. | 4.18.3 and 4.21.0 | Medium | Camel-Langchain4j-Tools: Tool argument headers are not filtered against declared parameters, allowing an LLM to inject arbitrary Exchange headers via tool call arguments |
| CVE-2026-48206 | From 4.0.0 before 4.14.8, from 4.15.0 before 4.18.3, from 4.19.0 before 4.21.0. | 4.14.8, 4.18.3 and 4.21.0 | Medium | Camel-JIRA: A set of non-Camel-prefixed Exchange header constants (IssueKey, ProjectKey, IssueTransitionId, ...) bypass the HTTP header filter, allowing an HTTP client to drive arbitrary JIRA issue operations using the endpoint's configured credentials |
| CVE-2026-48205 | From 4.0.0 before 4.14.8, from 4.15.0 before 4.18.3, from 4.19.0 before 4.21.0. | 4.14.8, 4.18.3 and 4.21.0 | Medium | Camel-DNS: The dns.* and term Exchange header constants used non-Camel-prefixed names that bypass the HTTP header filter, allowing an HTTP client to redirect DNS queries to an attacker-controlled server (server-side request forgery) and enumerate internal hostnames |
| CVE-2026-48204 | From 4.0.0 before 4.14.8, from 4.15.0 before 4.18.3, from 4.19.0 before 4.21.0. | 4.14.8, 4.18.3 and 4.21.0 | Medium | Camel-MongoDB-GridFS: The gridfs.* control headers used non-Camel-prefixed names that bypass the HTTP header filter, allowing an HTTP client to switch the GridFS operation - including destructive file deletion - in the default configuration |
| CVE-2026-48203 | From 4.0.0 before 4.14.8, from 4.15.0 before 4.18.3, from 4.19.0 before 4.21.0. | 4.14.8, 4.18.3 and 4.21.0 | Medium | Camel-Solr: The SolrParam. and SolrField. Exchange header prefixes used non-Camel-prefixed names that bypass the HTTP header filter, allowing an HTTP client to inject Solr query parameters (server-side request forgery) and document fields |
| CVE-2026-46726 | From 4.0.0 before 4.14.8, from 4.15.0 before 4.18.3, from 4.19.0 before 4.21.0. | 4.14.8, 4.18.3 and 4.21.0 | High | Camel-Vertx-Websocket: The inbound consumer maps externally-supplied WebSocket query and path parameters into the Exchange without a HeaderFilterStrategy, allowing injection of Camel control headers - enabling server-side request forgery and disclosure of secrets when bridged to an HTTP producer |
| CVE-2026-46592 | From 4.0.0 before 4.14.8, from 4.15.0 before 4.18.3, from 4.19.0 before 4.21.0. | 4.14.8, 4.18.3 and 4.21.0 | Medium | Camel-CXF: The SOAP operation-selection headers used non-Camel-prefixed names (operationName, operationNamespace) that bypass the HTTP header filter, allowing an HTTP client to redirect the invoked SOAP operation |
| CVE-2026-46591 | From 4.10.0 before 4.14.8, from 4.15.0 before 4.18.3, from 4.19.0 before 4.21.0. | 4.14.8, 4.18.3 and 4.21.0 | Medium | Camel-Neo4j: JSON property names from the CamelNeo4jMatchProperties header are interpolated into the Cypher WHERE clause without validation, allowing Cypher injection (incomplete remediation of CVE-2025-66169) |
| CVE-2026-46590 | From 4.18.0 before 4.18.3, from 4.19.0 before 4.21.0. | 4.18.3 and 4.21.0 | Medium | Camel-PQC: The HashiCorp Vault and AWS Secrets Manager key-lifecycle managers deserialize persisted key metadata with java.io.ObjectInputStream and no ObjectInputFilter (incomplete remediation of CVE-2026-40048) |
| CVE-2026-46588 | From 4.0.0 before 4.14.8, from 4.15.0 before 4.18.3, from 4.19.0 before 4.21.0. | 4.14.8, 4.18.3 and 4.21.0 | Medium | Camel-CouchDB: Non-Camel-prefixed Exchange headers bypass HeaderFilterStrategy allowing operation override from untrusted input |
| CVE-2026-46587 | From 4.0.0 before 4.14.8, from 4.15.0 before 4.18.3, from 4.19.0 before 4.21.0. | 4.14.8, 4.18.3 and 4.21.0 | Medium | Camel-Couchbase: Non-Camel-prefixed Exchange headers bypass HeaderFilterStrategy allowing operation override from untrusted input |
| CVE-2026-46585 | From 4.0.0 before 4.14.8, from 4.15.0 before 4.18.3, from 4.19.0 before 4.21.0. | 4.14.8, 4.18.3 and 4.21.0 | Medium | Camel-Lucene: The query control headers used non-Camel-prefixed names (QUERY, RETURN_LUCENE_DOCS) that bypass the HTTP header filter, allowing an HTTP client to inject the full-text search query |
| CVE-2026-46584 | From 4.0.0 before 4.14.8, from 4.15.0 before 4.18.3, from 4.19.0 before 4.21.0. | 4.14.8, 4.18.3 and 4.21.0 | Medium | Camel-Mail: The mail producer applied attacker-supplied mail.smtp.* / mail.smtps.* message headers as JavaMail session properties, allowing an attacker to weaken the SMTP transport security and, on releases before 4.19.0, redirect the connection and steal the configured SMTP credentials |
| CVE-2026-46457 | From 4.0.0 before 4.14.8, from 4.15.0 before 4.18.3, from 4.19.0 before 4.21.0. | 4.14.8, 4.18.3 and 4.21.0 | Medium | Camel-NATS: Inbound NATS message headers are mapped into the Exchange without a configured HeaderFilterStrategy, allowing a client that can publish to the subject to inject Camel control headers |
| CVE-2026-46456 | From 4.0.0 before 4.14.8, from 4.15.0 before 4.18.3, from 4.19.0 before 4.21.0. | 4.14.8, 4.18.3 and 4.21.0 | Medium | Camel-AWS2-SQS: Inbound message attributes are mapped into the Exchange without an inbound HeaderFilterStrategy, allowing a message sender to inject Camel control headers |
| CVE-2026-46455 | From 4.18.0 before 4.18.3, from 4.19.0 before 4.21.0. | 4.18.3 and 4.21.0 | Medium | Camel-Keycloak: The access-token validity window is not verified because the IS_ACTIVE check is missing from the TokenVerifier, allowing expired tokens to be accepted |
| CVE-2026-46454 | From 4.0.0 before 4.14.8, from 4.15.0 before 4.18.3, from 4.19.0 before 4.21.0. | 4.14.8, 4.18.3 and 4.21.0 | Medium | Camel-Cometd: Inbound Bayeux message headers are mapped into the Exchange without a HeaderFilterStrategy, allowing unauthenticated clients to inject Camel control headers |
| CVE-2026-46453 | From 4.3.0 before 4.14.8, from 4.15.0 before 4.18.3, from 4.19.0 before 4.21.0. | 4.14.8, 4.18.3 and 4.21.0 | Medium | Camel-Elasticsearch-Rest-Client: Exchange header constants without the Camel prefix bypass inbound HTTP header filtering, allowing untrusted clients to override the Elasticsearch query and operation |
| CVE-2026-43865 | From 4.0.0 before 4.14.8, from 4.15.0 before 4.18.3, from 4.19.0 before 4.21.0. | 4.14.8, 4.18.3 and 4.21.0 | Medium | Camel-Hazelcast: Unsafe Java deserialization in default-configured managed Hazelcast instances enables remote code execution |
| CVE-2026-40859 | From 4.0.0 before 4.14.8, from 4.15.0 before 4.18.3, from 4.19.0 before 4.20.0. | 4.14.8, 4.18.3 and 4.20.0 | Medium | Camel-Vertx-Http and Camel-Netty-Http: Unsafe Java deserialization of HTTP response bodies via a raw ObjectInputStream when transferException is enabled |
| CVE-2026-40047 | From 4.15.0 before 4.18.3. | 4.18.3 and 4.19.0 | Medium | Camel-Docling: Insufficient validation of custom CLI arguments enables argument injection and path traversal in DoclingProducer |
| CVE-2026-47323 | from 3.18.0 before 4.14.6, from 4.15.0 before 4.18.2, from 4.19.0 before 4.19.0 | 4.14.6, 4.18.2 and 4.19.0 | Medium | Camel-CXF and Camel-Knative Message Header Injection via Missing Inbound Filtering |
| CVE-2026-45760 | This issue affects Apache Camel K: from 2.0.0 before 2.8.1, from 2.9.0 before 2.9.2, from 2.10.0 before 2.10.1. | 2.8.1, 2.9.2 and 2.10.1 | High | Camel K Cross-Namespace Build Deputy Attack |
| CVE-2026-33453 | From 4.14.0 before 4.14.6, from 4.15.0 before 4.18.1. | 4.14.6, 4.18.1 and 4.19.0 | High | Apache Camel: Improperly Controlled Modification of Dynamically-Determined Object Attributes vulnerability in Camel-Coap component. |
| CVE-2026-42527 | Apache Camel 4.14.0 through 4.14.7 (4.14.x line). Apache Camel 4.18.0 through 4.18.2 (4.18.x line). Apache Camel 4.20.0. | 4.14.8, 4.18.3, 4.21.0. | Medium | Permissive default ObjectInputFilter pattern admits java.net.** and enables DNS-based information disclosure |
| CVE-2026-40860 | From 3.0.0 before 4.14.7, from 4.15.0 before 4.18.2, and from 4.19.0 before 4.20.0. | 4.14.7, 4.18.2 and 4.20.0 | High | Unsafe Deserialization of JMS ObjectMessage in camel-jms, camel-sjms, camel-sjms2 and camel-amqp |
| CVE-2026-40858 | From 4.0.0 before 4.14.7, from 4.15.0 before 4.18.2, from 4.19.0 before 4.20.0 | 4.14.7, 4.18.2 and 4.20.0 | High | Camel-Infinispan: Unsafe Deserialization in ProtoStream Remote Aggregation Repository |
| CVE-2026-40473 | From 3.0.0 before 4.14.6, from 4.15.0 before 4.18.2, from 4.19.0 before 4.20.0. | 4.14.6, 4.18.2 and 4.20.0 | Medium | Camel-Mina: Unsafe Deserialization in MinaConverter.toObjectInput() via TCP/UDP |
| CVE-2026-40453 | From 3.0.0 before 4.14.6, from 4.15.0 before 4.18.2, from 4.19.0 before 4.20.0. | 4.14.6, 4.18.2 and 4.20.0 | Medium | Incomplete fix for CVE-2025-27636 in non-HTTP HeaderFilterStrategies (camel-jms, camel-sjms, camel-coap, camel-google-pubsub) allows case-variant header injection |
| CVE-2026-40048 | From 4.19.0 before 4.20.0, from 4.18.0 before 4.18.2. | 4.18.2 and 4.20.0 | High | Camel-PQC: Unsafe Deserialization from FileBasedKeyLifecycleManager |
| CVE-2026-40022 | From 4.14.1 before 4.14.6, from 4.15.0 before 4.18.2. | 4.14.6, 4.18.2 and 4.20.0 | Medium | Camel-Platform-HTTP-Main: Authentication Bypass on Non-Root Context Paths in camel main runtime |
| CVE-2026-33454 | From 3.0.0 before 4.14.6, from 4.15.0 before 4.18.1. | 4.14.6, 4.18.1 and 4.19.0 | High | Camel-Mail Message Header Injection via Improper Filtering |
| CVE-2026-27172 | From 3.0.0 before 4.14.6 and from 4.15.0 before 4.18.1 | 4.14.6, 4.18.1 and 4.19.0 | High | Apache Camel: Unsafe Java deserialization in camel-consul ConsulRegistry allows arbitrary code execution via malicious values read from the Consul KV store |
| CVE-2026-25747 | From 3.0.0 before 4.10.9, from 4.11.0 before 4.14.5, from 4.15.0 before 4.18.0. | 4.10.9, 4.14.5 and 4.18.0 | High | Apache Camel: Camel-LevelDB: Unsafe Deserialization from LevelDBAggregationRepository |
| CVE-2026-23552 | From 4.15.0 before 4.18.0. | 4.18.0 | High | Apache Camel: Camel-Keycloak: Cross-Realm Token Acceptance in KeycloakSecurityPolicy |
| CVE-2025-66169 | Apache Camel 4.10.x before 4.10.8, Apache Camel 4.14.x before 4.14.3, Apache Camel 4.15.0 and 4.16.0. | 4.10.8, 4.14.3 and 4.17.0 | Medium | Cypher injection vulnerability in Camel-Neo4j component |
| 2025 | ||||
| CVE-2025-30177 | Apache Camel 4.10.0 before 4.10.3. Apache Camel 4.8.0 before 4.8.6. | 4.8.6 and 4.10.3 | Medium | Camel-Undertow Message Header Injection via Improper Filtering |
| CVE-2025-29891 | Apache Camel 4.10.0 before 4.10.2. Apache Camel 4.8.0 before 4.8.5. Apache Camel 3.10.0 before 3.22.4. | 3.22.4, 4.8.5 and 4.10.2 | High | Camel Message Header Injection through request parameters |
| CVE-2025-27636 | Apache Camel 4.10.0 before 4.10.2. Apache Camel 4.8.0 before 4.8.5. Apache Camel 3.10.0 before 3.22.4. | 3.22.4, 4.8.5 and 4.10.2 | Medium | Camel Message Header Injection via Improper Filtering |
| 2024 | ||||
| CVE-2024-22371 | From 3.0.0 before 3.21.4, from 3.22.0 before 3.22.1, from 4.0.0 before 4.0.4, from 4.1.0 before 4.4.0 | 3.21.4, 3.22.1, 4.0.4 and 4.4.0 | Low | Exposure of sensitive data by by crafting a malicious EventFactory and providing a custom ExchangeCreatedEvent that exposes sensitive data |
| CVE-2024-23114 | From 3.0.0 before 3.21.4, from 3.22.0 before 3.22.1, from 4.0.0 before 4.0.4, from 4.1.0 before 4.4.0. | 3.21.4, 3.22.1, 4.0.4 and 4.4.0 | High | Apache Camel: Camel-CassandraQL: Unsafe Deserialization from CassandraAggregationRepository |
| CVE-2024-22369 | From 3.0.0 before 3.21.4, from 3.22.0 before 3.22.1, from 4.0.0 before 4.0.4, from 4.1.0 before 4.4.0. | 3.21.4, 3.22.1, 4.0.4 and 4.4.0 | High | Apache Camel: Camel-SQL: Unsafe Deserialization from JDBCAggregationRepository |
| 2023 | ||||
| CVE-2023-34442 | 3.0.0 up to 3.14.8, and 3.18.0 up to 3.18.7, 3.20.0 up to 3.20.5 and 4.0.0-M1 up to 4.0.0-M3 | 3.14.9, 3.18.8, 3.20.6, 3.21.0 and 4.0.0-RC1 | Low | Temporary File Local Information Disclosure in camel-jira |
| 2022 | ||||
| CVE-2022-45046 | 3.0.0 up to 3.14.5, and 3.15.0 up to 3.18.3, and 3.19.0. | 3.14.6, 3.18.4 | Medium | LDAP Injection in camel-ldap |
| 2021 | ||||
| No issues reported | ||||
| 2020 | ||||
| CVE-2020-11994 | 2.22.x, 2.23.x, 2.24.x, 2.25.0 and 2.25.1, 3.0.0 up to 3.3.0 | 2.25.2, 3.4.0 | Medium | Server-Side Template Injection and arbitrary file disclosure on Camel templating components |
| CVE-2020-11973 | 2.22.x, 2.23.x, 2.24.x, 2.25.0, 3.0.0 up to 3.1.0 | 2.25.1, 3.2.0 | Medium | Apache Camel Netty enables Java deserialization by default |
| CVE-2020-11972 | 2.22.x, 2.23.x, 2.24.x, 2.25.0, 3.0.0 up to 3.1.0 | 2.25.1, 3.2.0 | Medium | Apache Camel RabbitMQ enables Java deserialization by default |
| CVE-2020-11971 | 2.22.x, 2.23.x, 2.24.x, 2.25.x, 3.0.0 up to 3.1.0 | 3.2.0 | Medium | Apache Camel JMX Rebind Flaw Vulnerability |
| 2019 | ||||
| CVE-2019-0188 | Apache Camel versions prior to 2.24.0 | 2.24.0 | Medium | Apache Camel-XMLJson vulnerable to XML external entity injection (XXE) |
| CVE-2019-0194 | 2.21.0 up to 2.21.3, 2.22.0 up to 2.22.2, 2.23.0 | 2.21.5, 2.22.3, 2.23.1 | Medium | Apache Camel's File is vulnerable to directory traversal |
| 2018 | ||||
| CVE-2018-8041 | 2.20.0 up to 2.20.3, 2.21.0 up to 2.21.1, 2.22.0 | 2.20.4, 2.21.1, 2.22.1 and newer | Medium | Apache Camel's Mail is vulnerable to path traversal |
| CVE-2018-8027 | 2.20.0 up to 2.20.3, 2.21.0 | 2.20.4, 2.21.1 and newer | Medium | Apache Camel's Core is vulnerable to XXE in XSD validation processor |
| 2017 | ||||
| CVE-2017-12634 | 2.19.0 up to 2.19.3, 2.20.0 | 2.19.4, 2.20.1 and newer | Medium | Apache Camel's Castor unmarshalling operation is vulnerable to Remote Code Execution attacks |
| CVE-2017-12633 | 2.19.0 up to 2.19.3, 2.20.0 | 2.19.4, 2.20.1 and newer | Medium | Apache Camel's Hessian unmarshalling operation is vulnerable to Remote Code Execution attacks |
| CVE-2016-8749 | 2.16.0 up to 2.16.4, 2.17.0 up to 2.17.4, 2.18.0 up to 2.18.1 | 2.16.5, 2.17.5, 2.18.2 | Medium | Apache Camel's Jackson and JacksonXML unmarshalling operation are vulnerable to Remote Code Execution attacks |
| CVE-2017-5643 | 2.17.0 up to 2.17.5, 2.18.0 up to 2.18.2 | 2.17.6, 2.18.3 and newer | Medium | Apache Camel's Validation Component is vulnerable against SSRF via remote DTDs and XXE |
| CVE-2017-3159 | 2.17.0 up to 2.17.4, 2.18.0 up to 2.18.1 | 2.17.5, 2.18.2 and newer | Medium | Apache Camel's Snakeyaml unmarshalling operation is vulnerable to Remote Code Execution attacks |
| 2016 | ||||
| CVE-2015-5348 | 2.15.0 up to 2.15.4, 2.16.0 | 2.15.5, 2.16.1 and newer | Medium | Apache Camel's Jetty/Servlet usage is vulnerable to Java object de-serialisation vulnerability. |
| CVE-2015-5344 | 2.15.0 up to 2.15.4, 2.16.0 | 2.15.5, 2.16.1 and newer | Medium | Apache Camel's XStream usage is vulnerable to Remote Code Execution attacks. |
| 2015 | ||||
| CVE-2015-0264 | 2.13.0 up to 2.13.3, 2.14.0 up to 2.14.1 | 2.13.4, 2.14.2, 2.15.0 and newer | Medium | The XPath handling in Apache Camel for invalid XML Strings or invalid XML GenericFile objects allows remote attackers to read arbitrary files via an XML External Entity (XXE) declaration. The XML External Entity (XXE) will be resolved before the Exception is thrown. |
| CVE-2015-0263 | 2.13.0 up to 2.13.3, 2.14.0 up to 2.14.1 | 2.13.4, 2.14.2, 2.15.0 and newer | Medium | The XML converter setup in Apache Camel allows remote attackers to read arbitrary files via an SAXSource containing an XML External Entity (XXE) declaration. |
| 2014 | ||||
| CVE-2014-0003 | 2.11.0 up to 2.11.3, 2.12.0 up to 2.12.2 | 2.11.4, 2.12.3, 2.13.0 and newer | Critical | The Apache Camel XSLT component allows XSL stylesheets to perform calls to external Java methods. |
| CVE-2014-0002 | 2.11.0 up to 2.11.3, 2.12.0 up to 2.12.2 | 2.11.4, 2.12.3, 2.13.0 and newer | Critical | The Apache Camel XSLT component will resolve entities in XML messages when transforming them using an xslt route. |
| 2013 | ||||
| CVE-2013-4330 | 2.9.0 up to 2.9.7, 2.10.0 up to 2.10.6, 2.11.0 up to 2.11.1, 2.12.0 | 2.9.8, 2.10.7, 2.11.2, 2.12.1 and newer | Critical | Writing files using FILE or FTP components, can potentially be exploited by a malicious user. |