CVE-2026-47323
CriticalCVSS 9.8Exploitation Probability (EPSS)
Elevated risk70th percentile - higher than 70% of all known CVEs
Summary
Apache Camel vulnerability allows injection of internal headers via untrusted HTTP requests to CXF and Knative endpoints. Missing inbound header filtering lets an attacker override critical Camel headers, potentially leading to remote code execution or arbitrary file writes.
Risk Assessment
The organization is at risk of remote code execution (RCE) or unauthorized file writes if Camel routes forward messages from vulnerable endpoints to header-driven components like camel-exec or camel-file.
Recommendation
Upgrade Apache Camel to version 4.19.0, 4.18.2 (for 4.18.x LTS), or 4.14.6 (for 4.14.x LTS) immediately. As a temporary measure, deploy WAF rules to block suspicious headers.
Original NVD description (English source)
Camel-CXF and Camel-Knative Message Header Injection via Missing Inbound Filtering The CXF and Knative HeaderFilterStrategy implementations (CxfRsHeaderFilterStrategy in camel-cxf-rest, CxfHeaderFilterStrategy in camel-cxf-transport, and KnativeHttpHeaderFilterStrategy in camel-knative-http) only filter outbound Camel-internal headers via setOutFilterStartsWith, while not configuring inbound filtering via setInFilterStartsWith. As a result, an unauthenticated attacker can inject Camel-internal headers (e.g. CamelExecCommandExecutable, CamelFileName) via HTTP requests to CXF-RS or CXF-SOAP endpoints. When a route forwards messages from these endpoints to header-driven components such as camel-exec or camel-file, the injected headers override configured values, enabling remote code execution or arbitrary file writes. This is the same pattern that was previously addressed in camel-undertow (CVE-2025-30177), the broader incoming-header filter (CVE-2025-27636 and CVE-2025-29891), and non-HTTP strategies (CVE-2026-40453). This issue affects Apache Camel: from 3.18.0 before 4.14.6, from 4.15.0 before 4.18.2. Users are recommended to upgrade to version 4.19.0, which fixes the issue. If users are on the 4.18.x LTS releases stream, then they are suggested to upgrade to 4.18.2. If users are on the 4.14.x LTS releases stream, then they are suggested to upgrade to 4.14.6.