Critical [CVE-2026-104286] Improper limitation of a pathname to a restricted directory
This critical-severity Fortinet advisory covers CVE-2026-104286 affecting FortiMail.
Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.
VulniPulse record published Record updated
Android app · Google Play
Monitor future Fortinet CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.
Summary
CVSSv3 Score:
9.8
An Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') [CWE-22] and Improper Neutralization of NULL Byte or NULL Character [CWE-158] vulnerability may allow an unauthenticated attacker to write arbitrary files on the underlying system via crafted HTTP or HTTPS requests.
This has been reported to be exploited in the wild, customers are urged to apply the workaround below.
Revised on 2026-10-07 00:00:00
Affected product named by the advisory: FortiMail.
CISA Known Exploited Vulnerability
- Listed:
- Oct 1, 2026 · federal remediation due Oct 4, 2026
- Required action:
- Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
- Ransomware use:
- Unknown
KEV is a prioritization signal from CISA — remediation detail still comes from the vendor advisory.
- FortiMail: 7.0.0 through 8.0.0 (vendor-listed versions)
Official advisory · high-confidence parse· fetched 5 days ago·verify at source
Fixed versions
No fixed release is recorded yet. That does not prove no patch exists — confirm against the vendor advisory.
Official advisory · high-confidence parse· fetched 5 days ago·verify at source
Mitigation checklist
- This has been reported to be exploited in the wild, customers are urged to apply the workaround below.
Official advisory · high-confidence parse· fetched 5 days ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.