Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
Critical

Apache Camel camel-mail inbound header injection leading to route manipulation and possible RCE

IdentifiersCVE-2026-33454CWE-74

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.

Share:
For your environment

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.

ANALYST BRIEF

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.

Successful exploitation allows a remote attacker who can deliver email to a monitored mailbox to inject attacker-controlled Camel headers into inbound exchanges. This can alter downstream route behavior and, depending on how the route uses affected components such as camel-bean, camel-exec, or camel-sql, may lead to remote code execution, command execution, unintended SQL operations, or other unsafe processing. At minimum, the flaw enables untrusted external input to manipulate internal routing and component behavior across the Camel pipeline.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, reduce exposure by restricting who can send mail to mailboxes consumed by camel-mail, especially blocking untrusted external senders; validating, sanitizing, or explicitly stripping Camel-prefixed headers from inbound messages before they reach downstream components; and avoiding route designs that trust inbound headers to control sensitive behavior in components such as camel-bean, camel-exec, or camel-sql. Additional compensating controls include isolating mail-ingestion routes and minimizing use of dangerous downstream components on untrusted mail flows.

Remediation

Patch, then assume compromise.

Upgrade Apache Camel to a fixed release. Apache recommends upgrading to 4.19.0. For supported LTS streams, upgrade 4.14.x to 4.14.6 or later, or 4.18.x to 4.18.1 or later. These releases address the missing inbound header filtering in the camel-mail component.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

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.

VendorProductType
Apache Software FoundationCamelapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

ACTIVITY FEED

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.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity7

Community discussion across Reddit, Mastodon, and other social sources.