CVE-2025-54972: Fortinet FortiMail · Information Disclosure
Affects Fortinet FortiMailSource CVE Database V5
Public exploit available · CVSS 3.9 Low.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 11% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N/E:P/RL:O/RC:CExploitation evidence
Disclosed: evidence found.
CVE published 18 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
CVSS exploit maturity: proof of concept public
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), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Fortinet FortiMail | Affected
| Fixed in– |
AI-suggested
- Monitor Fortinet advisories closely and apply official patches or updates as soon as they become available to address CVE-2025-54972.
- Implement strict URL filtering and email gateway policies to reduce the risk of users clicking on maliciously crafted links that could trigger the vulnerability.
- Educate users about the risks of clicking unknown or suspicious links, especially those received via email.
- Configure FortiMail and associated network devices to enforce strict HTTP header validation and sanitization where possible.
- Employ web application firewalls (WAFs) or intrusion prevention systems (IPS) that can detect and block CRLF injection attempts targeting FortiMail interfaces.
- Conduct regular security assessments and penetration tests focusing on email security appliances to identify and remediate similar injection flaws proactively.
- Maintain comprehensive logging and monitoring of FortiMail HTTP traffic to detect unusual header manipulations or injection attempts.
- Segment FortiMail management interfaces from general user networks to limit exposure and reduce attack surface.
- Review and harden email security policies to minimize the impact of potential header injection attacks, including disabling unnecessary HTTP services or interfaces on FortiMail appliances.
Description
An improper neutralization of crlf sequences ('crlf injection') vulnerability in Fortinet FortiMail 7.6.0 through 7.6.3, FortiMail 7.4.0 through 7.4.5, FortiMail 7.2 all versions, FortiMail 7.0 all versions may allow an attacker to inject headers in the response via convincing a user to click on a specifically crafted link