Apache Camel is widely used in integration pipelines; inbound header injection can disrupt routing across many deployments.
CVE-2026-33454
Camel-Mail inbound header injection can alter route behavior.
Is CVE-2026-33454 being exploited?
Not confirmed. CVE-2026-33454 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.62% probability of exploitation in the next 30 days.
How severe is CVE-2026-33454?
CVE-2026-33454 is rated Critical with a CVSS score of 9.4. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-33454?
Yes. A fix has been recorded for CVE-2026-33454. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-33454 affect?
CVE-2026-33454 affects Apache Camel 3.0.0 - 4.14.6, Apache Camel 4.15.0 - 4.18.1. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-33454?
Upgrade to Camel 4.19.0 (4.18.1 for 4.18.x LTS; 4.14.6 for 4.14.x LTS).
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Inbound mail headers can be injected via Camel's mail consumer, altering downstream components (bean, exec, sql) and potentially disrupting routes.
Immediate action required
- affected>= 3.0.0 and < 4.14.6
- affected>= 4.15.0 and < 4.18.1
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.