dbcve.org
CamelApplication · Apache

CVE-2026-33454

CRITICAL · 9.4 CVSS v3.1 Published 2026-04-27
Fix available
A fix is available. Upgrade to 4.14.6 / 4.18.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Camel-Mail component has a header injection vulnerability where MailHeaderFilterStrategy only filters headers in the 'out' direction but not the 'in' direction. This allows attackers to inject Camel-specific headers via email into routes consuming from IMAP or POP3, potentially altering downstream route behavior in components like camel-bean, camel-exec, or camel-sql.

MitigationUpgrade Apache Camel to version 4.19.0 (or 4.18.1 for 4.18.x LTS, or 4.14.6 for 4.14.x LTS) to fix the missing inbound header filter configuration.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
CamelApplication
Affected:>= 3.0.0, < 4.14.6>= 4.15.0, < 4.18.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Apache Camel version
    Run 'camel --version' or check the Camel version in your pom.xml/dependencies (org.apache.camel:camel-core)
    Affected if version is >= 3.0.0 and < 4.14.6, or >= 4.15.0 and < 4.18.1
  2. Verify camel-mail component is in use
    Check your project's pom.xml or dependencies for 'org.apache.camel:camel-mail' or look for mail: endpoints in your Camel route definitions
    Affected if camel-mail dependency is present and used in routes
  3. Identify IMAP/POP3 consumer endpoints
    Search route configuration files (XML, Java, YAML) for 'mail:imap' or 'mail:pop3' URIs that consume inbound email
    Affected if routes contain mail:imap or mail:pop3 consumers receiving email from external sources
  4. Inspect MailHeaderFilterStrategy configuration
    Search codebase for 'MailHeaderFilterStrategy' instances and check if setInFilterStartsWith() is called with 'Camel' or similar prefixes to filter inbound headers
    Affected if no custom MailHeaderFilterStrategy is configured OR setInFilterStartsWith is not called with 'Camel' prefix to filter inbound headers

You are affected if your Camel version is in the vulnerable range, you use camel-mail with IMAP/POP3 consumers, and no inbound header filtering is configured via MailHeaderFilterStrategy.setInFilterStartsWith.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 4.14.6 / 4.18.1 or later
Fixed in 4.14.64.18.1
Interim mitigation

Upgrade Apache Camel to version 4.19.0 (or 4.18.1 for 4.18.x LTS, or 4.14.6 for 4.14.x LTS) to fix the missing inbound header filter configuration.

Recommended fix High confidence

4.19.0 (or 4.18.1 for 4.18.x LTS, or 4.14.6 for 4.14.x LTS)

  1. 1. Identify the current Apache Camel version in use by checking your project dependencies (pom.xml, build.gradle, or equivalent)
  2. 2. Determine which LTS release stream you are on (4.14.x, 4.18.x, or another version)
  3. 3. For users on 4.14.x LTS: upgrade Apache Camel to version 4.14.6
  4. 4. For users on 4.18.x LTS: upgrade Apache Camel to version 4.18.1
  5. 5. For users on any other affected version: upgrade to version 4.19.0
  6. 6. Update the camel-mail dependency version in your build configuration (e.g., pom.xml: <version>4.14.6</version> or the appropriate version for your stream)
  7. 7. Rebuild and test your application to verify the upgrade does not break existing functionality
  8. 8. Redeploy the updated application
Caveat Review release notes for the target version as minor/major upgrades may include breaking changes in other Camel components

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Camel Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-33454 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-33454 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data