Improper certificate validation in Fortinet FortiOS enables SSLVPN MitM attacks

Note: This data is for reference and cybersecurity research purposes only.CyStack advises users not to use this information for unlawful purposes.

What is CVE-2026-121528?

CVE-2026-121528 is a vulnerability classified as Improper Certificate Validation, affecting FortiOS (affected versions: 7.6.0 – ≤ 7.6.4, 7.4.0 – ≤ 7.4.9, and other affected versions). This vulnerability is rated High, with a CVSS score of 8.1. There is not enough data to determine whether this vulnerability has been exploited.

Overview

Original source data

A improper certificate validation vulnerability in Fortinet FortiOS 7.6.0 through 7.6.4, FortiOS 7.4.0 through 7.4.9, FortiOS 7.2.0 through 7.2.13 may allow a remote and unauthenticated attacker to perform a Man-in-the-Middle attack on the communication channel between the SSLVPN web portal and the backend destination website.

Affected products and scope

Fortinet FortiOS has defaultStatus set to unaffected, but the following branches are recorded as affected:

  • FortiOS 7.6.0 through 7.6.4.
  • FortiOS 7.4.0 through 7.4.9.
  • FortiOS 7.2.0 through 7.2.13.
  • FortiOS 7.0.0 through 7.0.19.
  • FortiOS 6.4.0 through 6.4.16.

The initial vulnerability description names only the 7.6, 7.4, and 7.2 branches, but the normalized affected facts also include the 7.0 and 6.4 branches. The status of versions or branches outside these ranges is not established by the available record.

Technical details

Fortinet FortiOS improperly validates certificates on the communication channel between the SSLVPN web portal and the backend destination website. The weakness can allow a remote, unauthenticated attacker to conduct a Man-in-the-Middle attack against that network communication. The available record does not describe the precise condition that lets an attacker obtain or use an interception position. It also does not identify the specific certificate-validation implementation detail that fails, so the affected SSLVPN deployment path should be verified for each system.

Exploitability

The flaw is remotely reachable over the network and does not require authentication or user interaction. The supplied assessment characterizes attack complexity as high, indicating that additional conditions are needed even though credentials are not required. The record does not confirm exploitation in the wild, a public exploit, or an association with a ransomware campaign. Public detail about how an attacker would position themselves between the SSLVPN portal and backend website is limited.

Technical impact

The weakness reduces assurance that the backend website on the SSLVPN communication path is the intended endpoint. If an attacker achieves the conditions needed for MitM, traffic on the channel could be read or modified, potentially affecting the confidentiality and integrity of sessions or transactions. The supplied assessment also includes availability impact, but it does not explain a specific mechanism for causing service disruption. The record provides no evidence that a particular account, device, or dataset has been compromised.

Business impact

  • A successful MitM attack could expose data transmitted between the SSLVPN web portal and the backend website.
  • An attacker could alter traffic or responses on the channel, affecting the integrity of transactions or content delivered to users.
  • Interference could affect the availability or operation of the communication flow, but the specific disruption mechanism is not confirmed.
  • The actual data, sessions, and services at risk depend on the organization's SSLVPN and backend deployment. The record does not confirm a particular compromise or data breach.

Remediation

  1. Upgrade FortiOS using the supplied upgrade targets: move the 7.6 branch to 7.6.5, the 7.4 branch to 7.4.10, the 7.2 branch to 7.2.14, or use FortiOS 8.0.0 where that release is the applicable deployment target.
  2. For FortiOS 7.0.0 through 7.0.19 and 6.4.0 through 6.4.16, the record does not provide a corresponding fixed release. Confirm the appropriate upgrade target with Fortinet before selecting a remediation for either branch.
  3. Prioritize devices running the SSLVPN web portal with connections to backend destination websites, because that is the channel described as vulnerable.
  4. If an upgrade cannot be completed, obtain a Fortinet-supported mitigation for the specific branch and configuration. The current record supplies no concrete mitigation, so a configuration change should not be assumed to provide adequate protection.
  5. After upgrading, recheck the inventory and verify the installed version on each device rather than relying only on a change plan or package label.

Detection

  • Inventory all Fortinet FortiOS devices and compare the exact installed branch and version with the affected ranges.
  • Identify deployments that use the SSLVPN web portal to connect to backend destination websites, because this is the communication path named in the vulnerability description.
  • Review certificate-validation and TLS behavior for SSLVPN-to-backend sessions where corresponding telemetry is available.
  • Look for anomalous certificates, modified responses, or unexpected changes in connection behavior. Treat this as precautionary monitoring, not as a confirmed indicator of compromise.
  • Do not treat the absence of relevant log events as proof of safety; the record provides no specific log event or IOC.
Sources (5)
Learn more

Run an in-depth assessment with complete web risk management

CyStack VulnScan continuously discovers assets, validates vulnerabilities, and helps security teams prioritize remediation across the organization.