CVSS 3.1
3.7 lowCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:NLow (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.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:Norg.apache.camel:camel-mail (Maven): fixed in 4.14.8, 4.18.3, 4.21.0Explain 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.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| Apache Software Foundation Apache Camel Mail | from 4.0.0 before 4.14.8 |
| Apache Software Foundation Apache Camel Mail | from 4.15.0 before 4.18.3 |
| Apache Software Foundation Apache Camel Mail | from 4.19.0 before r |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-29vj-9mgp-mwp2 | Maven | org.apache.camel:camel-mail | >=4.0.0 <4.14.8 | 4.14.8 |
| GHSA-29vj-9mgp-mwp2 | Maven | org.apache.camel:camel-mail | >=4.15.0 <4.18.3 | 4.18.3 |
| GHSA-29vj-9mgp-mwp2 | Maven | org.apache.camel:camel-mail | >=4.19.0 <4.21.0 | 4.21.0 |
Red Hat rates this Moderate.
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.
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.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Build of Apache Camel 3.33.2.SP3 | org.apache.camel/camel-mail:4.18.3.redhat-00001 | Fixed 2026-07-30 | RHSA-2026:48118 |
| Red Hat build of Apache Camel 4.18.3 for Spring Boot 3.5.16 | camel-mail | Fixed 2026-08-13 | RHSA-2026:54622 |
| Red Hat build of Apache Camel 4 for Quarkus 3 | camel-mail | Affected | |
| Red Hat JBoss Enterprise Application Platform Expansion Pack | camel-mail | Not 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.
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.
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).