CVE-2026-66908High 7.5Apache Camel: 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 accepted0.6%
CVE-2026-66907High 7.5Apache Camel: Camel-Google-Storage: the consumer appended the remote object name to the configured downloadFileName directory without constraining the result0.8%
CVE-2026-66906Critical 9.1Apache Camel: Camel-Azure-Storage-Blob: the downloadBlobToFile operation built the local download target from the remote blob name without constraining it to the configured fileDir0.8%
CVE-2026-60093Medium 5.5Apache Camel: Camel-Azure-Storage-DataLake: the downloadToFile operation built the local download target from the remote path name without constraining it to the configured fileDir0.2%
CVE-2026-59230Medium 6.5Apache Camel: Camel-Mail: the MimeMultipart data format copied MIME headers onto the Camel message without a header filter strategy when unmarshalling with headersInline enabled0.7%
CVE-2026-43867Critical 9.8Apache Camel: Camel-PQC: The AWS Secrets Manager key-lifecycle manager deserializes persisted key metadata with java.io.ObjectInputStream and no ObjectInputFilter0.9%
CVE-2026-49365Medium 5.3Apache Camel: 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 clients0.6%
CVE-2026-49098Medium 5.3Apache Camel: 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 topic0.6%
CVE-2026-49097Medium 6.5Apache Camel: 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 users0.7%
CVE-2026-48204Critical 9.8Apache Camel: 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 configuration0.7%
CVE-2026-48203Critical 9.1Apache Camel: 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 fields0.6%
CVE-2026-46592High 7.5Apache Camel: 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 operation0.6%
CVE-2026-46591High 8.2Apache Camel: 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)0.5%
CVE-2026-46590High 8.8Apache Camel: 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)0.8%
CVE-2026-46457High 7.5Apache Camel: 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 headers0.7%
CVE-2026-46456Critical 9.8Apache Camel: Camel-AWS2-SQS: Inbound message attributes are mapped into the Exchange without an inbound HeaderFilterStrategy, allowing a message sender to inject Camel control headers0.8%
CVE-2026-46455Critical 9.8Apache Camel: 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 accepted0.7%
CVE-2026-46454Critical 9.8Apache Camel: Camel-Cometd: Inbound Bayeux message headers are mapped into the Exchange without a HeaderFilterStrategy, allowing unauthenticated clients to inject Camel control headers0.8%
CVE-2026-46453Medium 5.3Apache Camel: 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 operation0.6%
CVE-2026-42527High 8.1Apache Camel: Permissive default ObjectInputFilter pattern admits java.net.** and enables DNS-based information disclosure0.7%
CVE-2026-40859High 8.1Apache Camel: Camel-Vertx-Http: Unsafe Java deserialization of HTTP response bodies via a raw ObjectInputStream when transferException is enabled0.9%
CVE-2026-40047Critical 9.1Apache Camel: Camel-Docling: Insufficient validation of custom CLI arguments enables argument injection and path traversal in DoclingProducer2.4%
CVE-2026-27172High 8.8Apache Camel: Unsafe Java deserialization in camel-consul ConsulRegistry allows arbitrary code execution via malicious values read from the Consul KV store1.2%
CVE-2026-33453Critical 10.0Apache Camel: CoAP URI Query Parameter to Exchange Header Injection in camel-coap Allows Single-Packet Pre-Auth Remote Code Execution9.2%
CVE-2026-33454Critical 9.4Apache Camel: Inbound Header Filter Missing in MailHeaderFilterStrategy Allows Remote Code Execution via MIME Header Injection (CVE-2025-30177 Variant)1.5%
CVE-2026-40858High 8.8Apache Camel: Camel-Infinispan: Unsafe Deserialization in Remote Aggregation Repository1.3%
CVE-2026-40860Critical 9.8Apache Camel: Unsafe Deserialization of JMS ObjectMessage in camel-jms, camel-sjms, camel-sjms2 and camel-amqp1.7%
CVE-2026-23552Critical 9.1Apache Camel: Camel-Keycloak: Cross-Realm Token Acceptance Bypass in KeycloakSecurityPolicy0.6%
CVE-2025-30177Medium 6.5Apache Camel: Camel-Undertow Message Header Injection via Improper Filtering1.3%
CVE-2025-29891Medium 4.8Apache Camel: Camel Message Header Injection through request parameters76.1%
CVE-2025-27636Medium 5.6Apache Camel: Camel Message Header Injection via Improper Filtering97.1%
CVE-2024-22371Low 2.9Apache Camel issue on ExchangeCreatedEvent0.7%
CVE-2024-23114Critical 9.8Apache Camel: Camel-CassandraQL: Unsafe Deserialization from CassandraAggregationRepository1.3%
CVE-2024-22369High 7.8Apache Camel: Camel-SQL: Unsafe Deserialization from JDBCAggregationRepository0.7%