Apache Camel CVE-2026-33454

Exploitation requires: (1) a Camel application acting as a mail consumer via camel-mail, i.e. a route beginning from("imap://...") or from("pop3://...") monitoring a reachable mailbox; (2) at least one downstream component that acts on Camel headers - specifically camel-bean, camel-exec, or camel-sql - in the same route; and (3) the attacker's ability to deliver an email to that monitored mailbox. Limiting factors: this is NOT default behavior - a plain mail-to-storage route with no header-sensitive downstream component is not exploitable, and the injectable headers must reach a component whose behavior they can control; no authentication to the Camel host and no victim user interaction are required, but the specific route topology is the gating precondition.

Signals conflict, so prioritization needs judgment. The vendor CVSS 9.4 (AV:N/AC:L/PR:N/UI:N/C:H/I:H/A:L) reflects worst-case downstream impact assuming a vulnerable route topology, but exploitability is heavily conditional: it requires a Camel app that consumes mail via camel-mail AND passes those headers into a header-sensitive downstream component (camel-bean/exec/sql). EPSS is very low at 0.02% (6th percentile) and SSVC records Exploitation: none with Technical Impact only partial - but SSVC Automatable: yes indicates that where the preconditions exist, attacks can be scripted at scale by simply sending emails. There is no KEV listing and no public exploit identified. Net: a genuinely serious flaw for the subset of Camel deployments using mail consumers with dangerous downstream routing, but likely lower real-world urgency than the 9.4 suggests for typical deployments - the CVSS 'C:H/I:H' assumes the downstream RCE/SQL path is present, which is not the default.

An attacker learns that a target runs a Camel route consuming a shared mailbox (e.g., from("imap://orders@company.com") feeding a camel-exec or camel-sql step). They send a crafted email whose MIME headers carry Camel-specific header names (e.g., a command or SQL-controlling header); the unfiltered inbound mapping injects these into the Exchange, altering the downstream component's behavior. No authentication to the Camel host is needed and the action is automatable, though no public POC is currently identified.