Apache Camel's Camel-Mail component is vulnerable to Camel message header injection

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

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

EPSS

• CVE-2026-33454: 1.49% estimated exploitation activity in the next 30 days; percentile 74.16 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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:…

Published by the source

27 Apr 2026, 12:30 UTC

Last modified by the source

5 Oct 2026, 18:39 UTC

Source last checked

26 Oct 2026, 16:56 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-2vqf-x7g4-7c2g

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-33454

Advisory: Apache Camel's Camel-Mail component is vulnerable to Camel message header injection
IDs: CVE-2026-33454, GHSA-2vqf-x7g4-7c2g
Record: https://patchnext.com/advisories/cve-2026-33454 (revision 1, source checked 26 Oct 2026, 16:56 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.4)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.apache.camel:camel-mail 4.18.1, 4.14.6. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.apache.camel:camel-mail: affected >= 3.0.0, < 4.14.6; >= 4.15.0, < 4.18.1; fixed in 4.18.1, 4.14.6

## Suggested inspection (read-only)
- Maven org.apache.camel:camel-mail: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.apache.camel:camel-mail.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-2vqf-x7g4-7c2g (GitHub-reviewed advisory GHSA-2vqf-x7g4-7c2g lists affected ranges: Maven org.apache.camel:camel-mail >=3.0.0 =4.15.0 <4.18.1)

Commands are suggestions: review each one before running it.