Apache Camel Kafka CVE-2026-49098

Exploitation requires three conditions to be simultaneously true: first, the target deployment must run a Camel route that explicitly chains an HTTP consumer component (platform-http, camel-servlet, camel-jetty, or equivalent) into a kafka: producer - pure Kafka-to-Kafka routes, JMS-to-Kafka, or any non-HTTP ingress routes are entirely unaffected since HttpHeaderFilterStrategy is not involved. Second, the attacker must have HTTP access to that consumer endpoint; no credentials are required specifically when the HTTP consumer is unauthenticated, but if authentication is enforced the attacker must supply valid credentials. Third, the deployment must run an affected camel-kafka version (4.0.0-4.14.7, 4.15.0-4.18.2, or 4.19.0-4.20.x). Exploitation is further limited by the practical need to know a valid target Kafka topic name - while not a cryptographic control, it requires prior reconnaissance. The kafka.OVERRIDE_TIMESTAMP and kafka.PARTITION_KEY headers are similarly injectable, enabling message backdating and partition targeting respectively, but do not expand the access vector beyond the above conditions.

The vendor rates this vulnerability Moderate; no CVSS base vector or EPSS score was provided in the advisory, so quantitative signal comparison is unavailable. No CISA KEV listing exists and no public POC has been identified at time of analysis. Real-world risk is deployment-pattern-dependent: exploitation requires a Camel route that explicitly bridges an HTTP consumer into a kafka: producer - a pattern common in event-driven microservice integration but not universal. When that condition is met and the HTTP consumer is unauthenticated, the attack is trivially executable with a standard HTTP client and knowledge of a valid Kafka topic name, making the attack complexity effectively low. The primary business impact is integrity: an attacker can inject crafted messages into sensitive or critical Kafka topics consumed by downstream services, potentially manipulating payment flows, audit logs, or data pipelines. Secondary confidentiality impact exists if the attacker-chosen destination topic surfaces data they can observe. The vendor's Moderate rating likely reflects that the vulnerable route configuration is not the default Camel deployment mode. The discrepancy between the conditional ease of exploitation and the Moderate rating should prompt defenders to audit whether HTTP-to-Kafka bridge routes exist in their environments before dismissing this as low priority.

An attacker targeting a financial services platform discovers a public-facing Apache Camel HTTP endpoint (platform-http) that receives webhook events and routes them to a kafka://transactions.inbound topic for downstream processing. The attacker sends a POST request with the standard event payload but adds the HTTP header kafka.OVERRIDE_TOPIC: payments.settlement.confirmed - HttpHeaderFilterStrategy passes it unblocked, KafkaProducer.evaluateTopic() reads it as the authoritative destination, and the message lands in the settlements topic consumed by the payment finalization service rather than the intended inbound topic. No public exploit code exists, but the technique requires only curl and knowledge of an internal topic name obtainable through service documentation or error-message leakage.