Fortinet FortiMail

Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.

Lifecycle evidence status

This CVE identity is linked to the Lifecycle record Fortinet FortiMail. Use that record for publisher support phases and retirement dates.

A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.

CVE-observed version history

CVE	Published	Affected versions	Fixed version information	Publisher evidence
CVE-2022-39945	2 Nov 2022	FortiMail 7.2.0, 7.0.0 through 7.0.3, 6.4 all versions, 6.2 all versions, 6.0 all versions	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2022-26114	6 Sep 2022	FortiMail before 7.2.0	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2021-32586	1 Mar 2022	FortiMail before 7.0.1	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2021-36166	1 Mar 2022	FortiMail before 7.0.1	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2021-43062	2 Feb 2022	FortiMail 7.0.1, 7.0.0, 6.4.5, 6.4.4, 6.4.3, 6.4.2, 6.4.1, 6.4.0, 6.2.7, 6.2.6, 6.2.5, 6.2.4, 6.2.3, 6.2.2, 6.2.1, 6.2.0, 6.0.11, 6.0.10, 6.0.9, 6.0.8, 6.0.7, 6.0.6, 6.0.5, 6.0.4, 6.0.3, 6.0.2, 6.0.1, 6.0.0	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2020-15933	5 Jan 2022	FortiMail 6.4.1, 6.4.0, 6.2.4, 6.2.3, 6.2.2, 6.2.1, 6.2.0, 6.0.9, 6.0.8, 6.0.7, 6.0.6, 6.0.5, 6.0.4, 6.0.3, 6.0.2, 6.0.1, 6.0.0, 5.4.12, 5.4.11, 5.4.10, 5.4.9, 5.4.8, 5.4.7, 5.4.6, 5.4.5, 5.4.4, 5.4.3, 5.4.2, 5.4.1, 5.4.0, 5.3.13, 5.3.12, 5.3.10, 5.3.9, 5.3.8, 5.3.7, 5.3.6, 5.3.5, 5.3.4, 5.3.3, 5.3.2, 5.3.1, 5.3.0, 5.2.10, 5.2.9, 5.2.8, 5.2.7, 5.2.6, 5.2.5, 5.2.4, 5.2.3, 5.2.2, 5.2.1, 5.2.0, 5.1.7, 5.1.6, 5.1.5, 5.1.4, 5.1.3, 5.1.2, 5.1.1, 5.1.0, 5.0.11, 5.0.10, 5.0.9, 5.0.8, 5.0.7, 5.0.6, 5.0.5, 5.0.4, 5.0.3, 5.0.2, 5.0.1, 5.0.0, 4.3.9, 4.3.8, 4.3.7, 4.3.6, 4.3.5, 4.3.4, 4.3.3, 4.3.2, 4.3.1, 4.3.0, 4.2.4, 4.2.3, 4.2.2, 4.2.1, 4.2.0, 4.1.3, 4.1.2, 4.1.1, 4.1.0, 4.0.5, 4.0.4, 4.0.3, 4.0.1	An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.	Update reference ↗
CVE-2021-26095	20 Jul 2021	FortiMail 6.4.0 through 6.4.4 and 6.2.0 through 6.2.6	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2021-24013	12 Jul 2021	FortiMail before 6.4.4	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2021-24015	12 Jul 2021	FortiMail before 6.4.4	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2021-26090	12 Jul 2021	FortiMail 6.4.0 through 6.4.4 and 6.2.0 through 6.2.6	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2021-26099	12 Jul 2021	FortiMail before 7.0.0	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2021-24007	9 Jul 2021	FortiMail before 6.4.4	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2021-22129	9 Jul 2021	FortiMail before 6.4.5	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2021-26100	9 Jul 2021	FortiMail before 7.0.0	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2021-24020	9 Jul 2021	FortiMail 6.4.0 through 6.4.4, and 6.2.0 through 6.2.7	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record

How this record is maintained

The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.