Skip to content
Fencer Vulns
critical 9.4

CVE-2026-33454 in the critical feed json

Apache Camel: Inbound Header Filter Missing in MailHeaderFilterStrategy Allows Remote Code Execution via MIME Header Injection (CVE-2025-30177 Variant)

published 2026-04-27 6 mo ago modified 2026-10-26 13 d ago also EUVD-2026-25806 , GHSA-2vqf-x7g4-7c2g

cvss
9.4
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.5%
EPSS 1.5% chance of exploitation in 30 days, percentile 74%
public exploits
0
none known

Summary

The Camel-Mail component is vulnerable to Camel message header injection. The custom header filter strategy used by the component (MailHeaderFilterStrategy) only filters the 'out' direction via setOutFilterStartsWith, while it does not configure the 'in' direction via setInFilterStartsWith. As a result, when a Camel application consumes mail through camel-mail (for example via from(\"imap://...\") or from(\"pop3://...\")) the inbound filter check is skipped and Camel-prefixed MIME headers are mapped unfiltered into the Exchange. An attacker who can deliver an email to a mailbox monitored by such a consumer can inject Camel-specific headers that, for some Camel components downstream of the mail consumer (such as camel-bean, camel-exec, or camel-sql), can alter the behaviour of the route. This is the same pattern that was previously addressed in camel-undertow (CVE-2025-30177) and the broader incoming-header filter (CVE-2025-27636 and CVE-2025-29891).

This issue affects Apache Camel: from 3.0.0 before 4.14.6, from 4.15.0 before 4.18.1.

Users are recommended to upgrade to version 4.19.0, which fixes the issue. If users are on the 4.18.x LTS releases stream, then they are suggested to upgrade to 4.18.1. If users are on the 4.14.x LTS releases stream, then they are suggested to upgrade to 4.14.6.

Patch / fix

  • maven org.apache.camel:camel-mail 4.14.6, 4.18.1
  • Apache Software Foundation Apache Camel 4.14.6, 4.18.1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-33454 updated cvss 9.4

Apache Camel: Camel-Mail: Camel-Mail: Altered application behavior via header injection

  • Red Hat build of Apache Camel 4 for Quarkus 3 camel-mail
    affected: no fix available
  • Red Hat Build of Apache Camel 4.14 for Quarkus 3.27
    fixed: vendor fix RHSA-2026:19835
  • Red Hat build of Apache Camel 4.18.1 for Spring Boot 3.5.14
    fixed: vendor fix RHSA-2026:17668
  • Red Hat build of Apache Camel - HawtIO 4 camel-bean Red Hat build of Apache Camel 4 for Quarkus 3 camel-sql, camel-bean Red Hat build of Apache Camel for Spring Boot 4 camel-sql, camel-bean
    not affected: component not present
  • Red Hat Fuse 7 camel-sql, camel-bean, camel-mail Red Hat JBoss Enterprise Application Platform 7 camel-bean Red Hat JBoss Enterprise Application Platform 8 camel-sql, camel-bean, camel-mail Red Hat JBoss Enterprise Application Platform Expansion Pack camel-sql, camel-bean, camel-mail
    not affected: vulnerable code not present
  • Red Hat Process Automation 7 camel-sql
    not affected: component not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
6 mo ago

Exploit prediction

1.49% chance of exploitation in the next 30 days, higher than 74% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CISA ADP 3.1 9.4 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L
GitHub 3.1 9.4 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L
CNA 3.1 9.4 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L

Affected packages

ecosystem package affected fixed in
maven org.apache.camel:camel-mail
>=3.0.0, <4.14.6
>=4.15.0, <4.18.1
4.14.6
4.18.1

Affected products

  • Apache Software Foundation Apache Camel
  • Red Hat Red Hat Build of Apache Camel 4.14 for Quarkus 3.27
  • Red Hat Red Hat build of Apache Camel 4.18.1 for Spring Boot 3.5.14
  • Red Hat Red Hat build of Apache Camel 4 for Quarkus 3
  • Red Hat Red Hat build of Apache Camel for Spring Boot 4
  • Red Hat Red Hat build of Apache Camel - HawtIO 4
  • Red Hat Red Hat Fuse 7
  • Red Hat Red Hat JBoss Enterprise Application Platform 7
  • Red Hat Red Hat JBoss Enterprise Application Platform 8
  • Red Hat Red Hat JBoss Enterprise Application Platform Expansion Pack
  • Red Hat Red Hat Process Automation 7

Classification

Weakness
  • CWE-502 Deserialization of Untrusted Data
  • CWE-1173 Improper Use of Validation Framework
Technology feeds

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.