Fortinet: Improper certificate validation in RADIUS protocol
Patch in your next cycle: high severity (CVSS 7.5): sooner if the service is reachable from the Internet. How we decide
Which version to install
| Version or branch | Install |
|---|---|
| FortiAnalyzer 8.0 | 8.0.2 affected: 8.0.0 – 8.0.1 |
| FortiAnalyzer 7.6 | 7.6.8 affected: 7.6.0 – 7.6.7 |
| FortiAnalyzer 7.4 | 7.4.12 affected: 7.4.0 – 7.4.11 |
| FortiAnalyzer 7.2 | no fix in this branch: Fortinet says to move to a fixed release affected: 7.2 all versions |
| FortiAnalyzer Cloud 8.0 | 8.0.2 affected: 8.0.1 |
| FortiAnalyzer Cloud 7.6 | 7.6.8 affected: 7.6.0 – 7.6.7 |
| FortiAnalyzer Cloud 7.4 | 7.4.12 affected: 7.4.1 – 7.4.11 |
| FortiAnalyzer Cloud 7.2 | no fix in this branch: Fortinet says to move to a fixed release affected: 7.2 all versions |
| FortiManager 8.0 | 8.0.2 affected: 8.0.0 – 8.0.1 |
| FortiManager 7.6 | 7.6.8 affected: 7.6.0 – 7.6.7 |
| FortiManager 7.4 | 7.4.12 affected: 7.4.0 – 7.4.11 |
| FortiManager 7.2 | no fix in this branch: Fortinet says to move to a fixed release affected: 7.2 all versions |
| FortiManager Cloud 8.0 | 8.0.2 affected: 8.0.1 |
| FortiManager Cloud 7.6 | 7.6.8 affected: 7.6.0 – 7.6.7 |
| FortiManager Cloud 7.4 | 7.4.12 affected: 7.4.1 – 7.4.11 |
| FortiManager Cloud 7.2 | no fix in this branch: Fortinet says to move to a fixed release affected: 7.2 all versions |
| FortiSASE-Sovereign 26.2 | affected: 26.2 all versions |
| FortiSASE-Sovereign 25.4 | no fix in this branch: Fortinet says to move to a fixed release affected: 25.4 all versions |
| FortiSASE-Sovereign 25.3 | no fix in this branch: Fortinet says to move to a fixed release affected: 25.3 all versions |
| FortiSASE-Sovereign 25 | no fix in this branch: Fortinet says to move to a fixed release affected: 25 all versions |
From the vendor advisory table: check the exact build in the official advisory.
Published by the vendor November 10, 2026
In short
Improper certificate validation (CWE-295) in the RADIUS protocol implementation of FortiSASE Sovereign, FortiManager, FortiAnalyzer, FortiManager Cloud and FortiAnalyzer Cloud can let an attacker impersonate the RADIUS server. An attacker in a man-in-the-middle position can use a rogue RADIUS server to pose as the legitimate authentication server to affected devices.
Why it is dangerous
With a CVSS score of 7.5, the flaw can undermine authentication that relies on RADIUS. The attacker must be able to intercept traffic between the Fortinet product and the RADIUS server. No active exploitation has been reported.
What to do
- Apply the updates listed in Fortinet's official advisory FG-IR-26-247 to all affected products.
- Verify which FortiManager, FortiAnalyzer, cloud and FortiSASE Sovereign instances use RADIUS authentication and prioritize updating them.
- Restrict the network path between Fortinet devices and the RADIUS server to trusted, segmented networks to reduce the risk of interception.
- Monitor RADIUS authentication logs for anomalous logins or unexpected server responses until the update is applied.
Official advisory text
An Improper Certificate Validation vulnerability [CWE-295] in FortiSASE Sovereign, FortiManager, Fortianalyzer, FortiManager Cloud and FortiAnalyzer Cloud RADIUS protocol may allow a MITM attacker to impersonate the radius server via a rogue RADIUS server. Revised on 2026-11-10 00:00:00
Turn on Fortinet alerts
Details
- Vendor
- Fortinet
- Product
- FortiManager, FortiAnalyzer, FortiSASE Sovereign
- CVSS score
- 7.5
- Actively exploited
- Not known at this time
- Source
- Fortinet PSIRT – original advisory
- Published
- November 10, 2026
The summary is written with the help of an automated system from the public advisory and checked automatically for links and unsafe advice; severity, exploitation status and affected versions are compiled automatically from public sources and may contain errors. The vendor's original advisory prevails: check it before taking action. This information is provided without warranty and does not replace a professional assessment.
Sources last checked: 22 November 2026 at 09:15 (Italian time) · Report an error