A stack-based buffer overflow vulnerability in Fortinet FortiOS 7.4.0 through 7.4.1, FortiOS 7.2.0 through 7.…
- Severity
- High8.1CVSS 3.1, High
- EPSS
- 1%
- Published
- 12 Mar 2024
- Updated
- 8 Jul 2026
Description
Title, description and vendor guidance are quoted from the source records.
A stack-based buffer overflow vulnerability in Fortinet FortiOS 7.4.0 through 7.4.1, FortiOS 7.2.0 through 7.2.5, FortiOS 7.0.0 through 7.0.12, FortiOS 6.4.0 through 6.4.14, FortiOS 6.2.0 through 6.2.15, FortiProxy 7.4.0, FortiProxy 7.2.0 through 7.2.6, FortiProxy 7.0.0 through 7.0.12, FortiProxy 2.0.0 through 2.0.13, FortiSASE 23.2.b allows attacker to execute unauthorized code or commands via specially crafted HTTP requests.
Weakness: CWE-121
Known exploited
Not listed in CISA KEV as of the last check.
Exploit prediction
1% probability of exploitation in the next 30 days (percentile 64%).
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
What the source states, per branch
Versions matched by Patcharo
Fortinet FortiProxySource: Fortinet (CVE record)
| Branch | Affected | Fixed in |
|---|---|---|
| 7.4 | Exact releases: 7.4.0 | |
| 7.2 | 7.2.0 – 7.2.6 | Fixed after 7.2.6 |
| 7.0 | 7.0.0 – 7.0.12 | Fixed after 7.0.12 |
| 2.0 | 2.0.0 – 2.0.13 | Fixed after 2.0.13 |
Versions not listed are stated unaffected by the vendor.
Fortinet FortiOSSource: Fortinet (CVE record)
| Branch | Affected | Fixed in |
|---|---|---|
| 7.4 | 7.4.0 – 7.4.1 | Fixed after 7.4.1 |
| 7.2 | 7.2.0 – 7.2.5 | Fixed after 7.2.5 |
| 7.0 | 7.0.0 – 7.0.12 | Fixed after 7.0.12 |
| 6.4 | 6.4.0 – 6.4.14 | Fixed after 6.4.14 |
| 6.2 | 6.2.0 – 6.2.15 | Fixed after 6.2.15 |
Versions not listed are stated unaffected by the vendor.
Workaround / Vendor remediation
Vendor remediation · FortiProxy
Upgrade to FortiProxy version 7.4.1 or above Upgrade to FortiProxy version 7.2.7 or above Upgrade to FortiProxy version 7.0.13 or above Upgrade to FortiProxy version 2.0.14 or above Upgrade to FortiSwitchManager version 7.2.3 or above Upgrade to FortiSwitchManager version 7.0.3 or above Fortinet remediated this issue in FortiSASE version 23.3.b and hence customers do not need to perform any action. Upgrade to FortiOS version 7.4.2 or above Upgrade to FortiOS version 7.2.6 or above Upgrade to FortiOS version 7.0.13 or above Upgrade to FortiOS version 6.4.15 or above Upgrade to FortiOS version 6.2.16 or above Upgrade to FortiPAM version 1.2.0 or above
Vendor remediation · FortiOS
Upgrade to FortiProxy version 7.4.1 or above Upgrade to FortiProxy version 7.2.7 or above Upgrade to FortiProxy version 7.0.13 or above Upgrade to FortiProxy version 2.0.14 or above Upgrade to FortiSwitchManager version 7.2.3 or above Upgrade to FortiSwitchManager version 7.0.3 or above Fortinet remediated this issue in FortiSASE version 23.3.b and hence customers do not need to perform any action. Upgrade to FortiOS version 7.4.2 or above Upgrade to FortiOS version 7.2.6 or above Upgrade to FortiOS version 7.0.13 or above Upgrade to FortiOS version 6.4.15 or above Upgrade to FortiOS version 6.2.16 or above Upgrade to FortiPAM version 1.2.0 or above
References
Provenance
Every fact on this page comes from the sources below. Nothing is written by an AI.
- Fortinet (CVE record)
- Fortinet (CVE record) · 27 Sept 2026, 23:46 UTC · Parser patcharo-cve5/1.1.0
- NVD
- NVD · 27 Sept 2026, 23:44 UTC · Parser patcharo-nvd/1.0.0
- FIRST EPSS
- FIRST EPSS · 27 Sept 2026, 23:46 UTC · Parser patcharo-epss/1.0.0
Last verified: 28 Sept 2026, 02:31 UTC