Apache Camel camel-mail inbound header injection leading to route manipulation and possible RCE
CVE-2026-33454 is an important-severity vulnerability in Apache Camel's camel-mail component caused by incomplete header filtering in MailHeaderFilterStrategy. The strategy configures outbound filtering via setOutFilterStartsWith but does not configure inbound filtering via setInFilterStartsWith. As a result, when a Camel application consumes email through camel-mail, such as via from("imap://...") or from("pop3://..."), Camel-prefixed MIME headers from inbound messages are mapped into the Camel Exchange without being filtered. An attacker who can send email to a mailbox monitored by the vulnerable mail consumer can inject Camel-specific headers into the message flow. Those injected headers can influence downstream Camel components, including camel-bean, camel-exec, and camel-sql, altering route behavior and in some application designs enabling remote code execution or unsafe command/data handling.
Are you exposed to this one?
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Mitigation
If you can’t patch tonight, do this now.
Remediation
Patch, then assume compromise.
Exploits
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
Recent activity
7 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
The version that knows your environment.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.