cve.bz

CVE-2026-46584 apache camel: Improper Input Validation

3.7 lowEPSS 0.6%Fix available

Low (3.7) in apache camel. EPSS 0.6% estimated probability of exploitation activity in the next 30 days. Fixed in org.apache.camel:camel-mail 4.14.8, 4.18.3, 4.21.0.

On this page
Improper Input Validation, Exposure of Sensitive Information to an Unauthorized Actor vulnerability in Apache Camel Mail Component. The camel-mail producer (MailProducer.getSender) scanned the outgoing Exchange for message headers in the mail.smtp. / mail.smtps. namespace and, when any were present, built a per-message JavaMail sender with those values applied as JavaMail session properties, overriding the endpoint configuration. This namespace is Camel-internal - only MailProducer interprets it - and was not blocked by any HeaderFilterStrategy, so the values could originate from any inbound protocol (for example platform-http query parameters or request headers, or JMS / Kafka messages from untrusted producers) that feeds a route ending in an smtp / smtps producer without an intervening removeHeaders. The maximal impact is version-dependent: on releases before 4.19.0, setting mail.smtp.host redirects the SMTP connection to a server under the attacker's control, and because the producer then authenticates with the endpoint's configured username and password those credentials are transmitted to the attacker; on 4.19.0 and later the producer connects to the endpoint's configured host explicitly, so the reachable impact is limited to weakening transport security (for example mail.smtp.ssl.trust, mail.smtp.starttls.enable or mail.smtp.socks.host) and interception of the outgoing message rather than host redirect. Exploitation requires a route that channels untrusted input into the mail producer without stripping the namespace. This issue affects Apache Camel: from 4.0.0 before 4.14.8, from 4.15.0 before 4.18.3, from 4.19.0 before 4.21.0. Users are recommended to upgrade to version 4.21.0, which fixes the issue. If users are on the 4.14.x LTS releases stream, then they are suggested to upgrade to 4.14.8. If users are on the 4.18.x releases stream, then they are suggested to upgrade to 4.18.3. After upgrading, the per-message override is disabled by default; enable it only on trusted endpoints with useJavaMailSessionPropertiesFromHeaders=true. For deployments that cannot upgrade immediately, strip the namespace before the mail producer with removeHeaders('mail.smtp.*') and removeHeaders('mail.smtps.*') between any untrusted ingress and the smtp / smtps producer. Even with the opt-in enabled, route authors should still strip the namespace on any path that carries untrusted input.

Severity

CVSS 3.1

3.7 low
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
EPSS
0.6% (unchanged from 0.6% a week ago; 0.6% 30 days ago) estimated probability of exploitation activity in the next 30 days; 47th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-07-06. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-20 Improper Input Validation
CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
OWASP Top 10
A01:2025 Broken Access Control, A05:2025 Injection
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-46584 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-46584?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-46584?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-46584 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-46584

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-46584](https://cve.bz/cve/badge/CVE-2026-46584.svg)](https://cve.bz/cve/CVE-2026-46584)

HTML:

<a href="https://cve.bz/cve/CVE-2026-46584"><img src="https://cve.bz/cve/badge/CVE-2026-46584.svg" alt="CVE-2026-46584"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Apache Software Foundation Apache Camel Mailfrom 4.0.0 before 4.14.8
Apache Software Foundation Apache Camel Mailfrom 4.15.0 before 4.18.3
Apache Software Foundation Apache Camel Mailfrom 4.19.0 before r

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-29vj-9mgp-mwp2Mavenorg.apache.camel:camel-mail>=4.0.0 <4.14.84.14.8
GHSA-29vj-9mgp-mwp2Mavenorg.apache.camel:camel-mail>=4.15.0 <4.18.34.18.3
GHSA-29vj-9mgp-mwp2Mavenorg.apache.camel:camel-mail>=4.19.0 <4.21.04.21.0

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This Moderate impact flaw in the Apache Camel Mail Component arises from improper input validation, allowing remote attackers to exploit routes that channel untrusted input into the mail producer without explicit header stripping. Depending on the Apache Camel version, this could lead to credential exposure by redirecting SMTP connections to an attacker-controlled server or, in newer versions, to the weakening of transport security and interception of outgoing messages. Exploitation is contingent on the application's routing configuration.

Red Hat's mitigation

To mitigate this vulnerability, ensure that any Camel routes processing untrusted input and forwarding it to the mail producer explicitly strip the `mail.smtp.*` and `mail.smtps.*` header namespaces. This can be achieved by adding `removeHeaders('mail.smtp.*')` and `removeHeaders('mail.smtps.*')` to the route definition between the untrusted ingress and the SMTP/SMTPS producer.

ProductPackageStateAdvisory
Red Hat Build of Apache Camel 3.33.2.SP3org.apache.camel/camel-mail:4.18.3.redhat-00001Fixed 2026-07-30RHSA-2026:48118
Red Hat build of Apache Camel 4.18.3 for Spring Boot 3.5.16camel-mailFixed 2026-08-13RHSA-2026:54622
Red Hat build of Apache Camel 4 for Quarkus 3camel-mailAffected
Red Hat JBoss Enterprise Application Platform Expansion Packcamel-mailNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-46584.

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it.

  • oscerd/CVE-2026-46584 Harbor Check: matches CVE 0 stars, Java, created
    Reproducer for CVE-2026-46584: Apache Camel camel-mail mail.smtp.* header injection enabling credential theft via on-path SOCKS interceptio…

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-20 (51), CWE-200 (59).

References

Check your stackJSON