CVE-2025-29891

Apache Camel releases from 4.10.0 before 4.10.2, from 4.8.0 before 4.8.5, and from 3.10.0 before 3.22.4 contain a flaw (CWE-164) in the default incoming header filter that lets attacker-controlled values be treated as Camel-specific internal headers, altering the behavior of components such as camel-bean and camel-exec. It shares a root cause with CVE-2025-27636 and the same fix, but it is exploitable via ordinary HTTP request parameters or payload content, not only via explicit HTTP headers; all known Camel HTTP entry points, including camel-servlet, camel-jetty, camel-undertow, camel-platform-http, and camel-netty-http, are vulnerable out of the box. An unauthenticated remote attacker who can reach an affected application over HTTP could manipulate component behavior (for example via camel-bean or camel-exec), producing integrity and availability impact per the 4.8 CVSS score; exploitation requires high attack complexity and a route that uses particular vulnerable components. Affected users are those running internet-exposed Camel applications (or bundled Camel in downstream products) on the affected version ranges with such routes. No in-the-wild exploitation is confirmed in the data and it is not in CISA KEV, but a public PoC exists (Akamai) and EPSS assigns a 75.1% probability of exploitation within 30 days (99th percentile), indicating elevated risk.

What to do: Upgrade Apache Camel to 4.10.2 (4.10.x LTS), 4.8.5 (4.8.x LTS), or 3.22.4 (3.x releases), and patch downstream products that bundle affected Camel versions. Until patched, audit routes for components whose behavior is header-driven (notably camel-bean and camel-exec), strip or filter Camel-specific names from both HTTP headers and request parameters at the edge, and avoid exposing Camel HTTP endpoints directly to the internet.