FortiMail vulnerabilities: known CVEs & security history
Fortinet · Actively exploited · 47 tracked CVEs · 2 actively exploited · updated October 2026 · what is a CVE? →
This is the full list of known vulnerabilities (CVEs) across all FortiMail release lines — 47 in total, with 2 actively exploited in the wild. A CVE here doesn't mean your version is affected — check FortiMail's current status and the safe version to run.
Known FortiMail CVEs
Actively-exploited and most-severe first. Open any CVE for full details.
| CVE | Severity | CVSS | EPSS | Year |
|---|---|---|---|---|
| CVE-2026-104286⚡ exploited | critical | 9.8 | 2% | 2026 |
| CVE-2025-32756⚡ exploited | critical | 9.8 | 30% | 2025 |
| CVE-2023-47539 | critical | 9.8 | 1% | 2025 |
| CVE-2021-36166 | critical | 9.8 | 1% | 2022 |
| CVE-2021-24007 | critical | 9.8 | 1% | 2021 |
| CVE-2020-9294 | critical | 9.8 | 78% | 2020 |
| CVE-2023-36556 | high | 8.8 | 1% | 2023 |
| CVE-2021-24013 | high | 8.8 | 1% | 2021 |
| CVE-2021-22129 | high | 8.8 | 1% | 2021 |
| CVE-2022-27488 | high | 8.3 | 0% | 2023 |
| CVE-2022-22299 | high | 7.8 | 0% | 2022 |
| CVE-2021-32586 | high | 7.7 | 1% | 2022 |
| CVE-2021-26091 | high | 7.5 | 0% | 2025 |
| CVE-2021-26095 | high | 7.5 | 1% | 2021 |
| CVE-2021-24020 | high | 7.5 | 1% | 2021 |
| CVE-2025-53681 | high | 7.2 | 0% | 2026 |
| CVE-2021-24015 | high | 7.2 | 1% | 2021 |
| CVE-2019-15712 | high | 7.2 | 1% | 2020 |
| CVE-2024-46663 | medium | 6.7 | 0% | 2025 |
| CVE-2024-56497 | medium | 6.7 | 1% | 2025 |
| CVE-2021-42757 | medium | 6.7 | 0% | 2021 |
| CVE-2021-43062 | medium | 6.1 | 13% | 2022 |
| CVE-2017-7732 | medium | 6.1 | 2% | 2017 |
| CVE-2017-3125 | medium | 6.1 | 1% | 2017 |
| CVE-2021-26100 | medium | 5.9 | 0% | 2021 |
| CVE-2023-45582 | medium | 5.6 | 1% | 2023 |
| CVE-2023-36633 | medium | 5.4 | 0% | 2023 |
| CVE-2022-39945 | medium | 5.4 | 0% | 2022 |
| CVE-2022-26114 | medium | 5.4 | 0% | 2022 |
| CVE-2021-24008 | medium | 5.3 | 1% | 2025 |
| CVE-2020-15933 | medium | 5.3 | 1% | 2022 |
| CVE-2021-32591 | medium | 5.3 | 1% | 2021 |
| CVE-2021-26090 | medium | 5.3 | 1% | 2021 |
| CVE-2019-15707 | medium | 4.9 | 1% | 2020 |
| CVE-2023-33302 | medium | 4.7 | 0% | 2025 |
| CVE-2022-23439 | medium | 4.7 | 0% | 2025 |
| CVE-2022-26122 | medium | 4.7 | 0% | 2022 |
| CVE-2024-40588 | medium | 4.4 | 0% | 2025 |
| CVE-2021-26099 | medium | 4.4 | 1% | 2021 |
| CVE-2025-54972 | medium | 4.3 | 0% | 2025 |
| CVE-2024-47569 | medium | 4.3 | 0% | 2025 |
| CVE-2014-8617 | medium | 4.3 | 1% | 2015 |
| CVE-2013-1471 | medium | 4.3 | 2% | 2013 |
| CVE-2025-55717 | medium | 4 | 0% | 2026 |
| CVE-2015-3293 | medium | 4 | 1% | 2015 |
| CVE-2022-29056 | low | 3.7 | 2% | 2023 |
| CVE-2023-36637 | low | 3.5 | 0% | 2023 |
Is my FortiMail version affected?
The list above spans every release. To know whether your version is affected — and the minimum safe version to upgrade to — check it directly.
Check your FortiMail version → · Monitor FortiMail for new CVEs →
FortiMail vulnerabilities — frequently asked
How many known vulnerabilities does FortiMail have?
IsItPatched tracks 47 CVEs for FortiMail, 2 of which are actively exploited (CISA KEV). 6 are critical-severity and 12 high-severity. These span every release line — what matters is whether the version you run is affected.
Does FortiMail have any actively-exploited vulnerabilities?
Yes — 2 FortiMail CVEs are in CISA's Known Exploited Vulnerabilities catalog, meaning they are confirmed exploited in the wild. Patch these as a priority.
What is the most severe FortiMail vulnerability?
Among tracked issues, CVE-2026-104286 (CRITICAL, CVSS 9.8), which is actively exploited, ranks highest — a Path traversal weakness.
Is FortiMail safe to use?
It depends on the version. The latest supported FortiMail release clears the known issues; older versions may still be affected. Check the exact version you run for a verdict.
CVE data aggregated from NVD, CISA KEV and EPSS (FIRST.org). Related: FortiMail security status · FortiMail end-of-life · actively-exploited CVEs. Always verify against Fortinet's advisories — see our disclaimer.