CVE-2026-93576: Red Hat build of Apache Camel for Spring Boot 4 · CRLF Injection
Affects Red Hat build of Apache Camel for Spring Boot 4Source CVE Database V5
Not known to be exploited · CVSS 7.5 High.
Data as of 2 Nov 2026, 22:58 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 19% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 18 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Red HatRed Hat build of Apache Camel for Spring Boot 4 | Affected– | Fixed in– |
| Red HatRed Hat Fuse 7 | Affected– | Fixed in– |
| Red HatRed Hat JBoss Enterprise Application Platform 7 | Affected– | Fixed in– |
| Red HatRed Hat Single Sign-On 7 | Affected– | Fixed in– |
AI-suggested
Red Hat's advisory directs users to the Netty GitHub security advisories for fixed versions and remediation guidance (https://github.com/netty/netty/security/advisories/GHSA-5vh9-c45f-rf7p). Users should upgrade to fixed versions of netty-codec-smtp as recommended by the vendor. Since this is a component-level vulnerability, remediation involves updating the affected Netty library. No additional mitigations are specified by Red Hat. Patch status is confirmed via the vendor advisory.
Description
A flaw was found in Netty netty-codec-smtp. The component does not properly validate Carriage Return (CR) and Line Feed (LF) characters in the SMTP command-name field. A remote attacker, if an application routes untrusted input into this field, can embed CR/LF characters to inject arbitrary SMTP commands. This can lead to SMTP command smuggling, allowing for unauthorized email relay or spoofing of sender/recipient addresses. While the impact is significant, the real-world exploitability is considered lower as applications typically do not place user-controlled data in the command-name field.