Executive Summary

CVE-2026-121528 is an improper certificate validation flaw in the FortiOS SSL-VPN web portal that allows a remote, unauthenticated attacker to position themselves as a Man-in-the-Middle between the portal and the backend destination website. For OT environments that use FortiOS as the remote access boundary into control networks, this converts the VPN itself into an interception point rather than a trust anchor.

Technical Exposure Breakdown

The vulnerable component is the SSL-VPN web portal proxy function in FortiOS. When the portal brokers a connection from an external client to a backend destination, it does not correctly validate the certificate presented on the backend leg of the session. The GROUNDING DATA lists the affected ranges as FortiOS 7.6.0 through 7.6.4, 7.4.0 through 7.4.9, 7.2.0 through 7.2.13, 7.0.0 through 7.0.19, and 6.4.0 through 6.4.16. Patch status is listed as unknown, so operators should treat all deployed instances in these ranges as exposed until a fixed build is confirmed for their specific train.

The attack vector is network based and requires no authentication. An attacker who can sit on the path between the portal and the backend target, or who can manipulate DNS or routing to insert themselves on that path, can present a forged or substituted certificate that the portal accepts. From there the attacker reads and modifies traffic in clear. The assigned CVSS score is 8.1, consistent with a high impact confidentiality and integrity break that depends on an attacker achieving a network position rather than a simple single packet trigger.

The practical condition that matters for OT is this: the SSL-VPN web portal is almost always internet reachable by design. That is its job. The backend leg that is being spoofed may be an internal HMI web interface, an engineering workstation portal, a historian, or a vendor management console. Interception on that leg means the operator believes they are on an encrypted tunnel to a trusted internal asset while the attacker observes or alters the session.

OT Impact and Compliance Risk

In an OT remote access architecture the SSL-VPN portal is frequently the single enforced boundary between the outside world and the control environment. If that boundary silently accepts a forged backend certificate, several things break physically and procedurally. Credentials for engineering workstations and HMIs can be captured and replayed. Setpoint changes, firmware upload sessions, and configuration pushes delivered over the portal can be altered in transit. Because the manipulation happens inside a session the operator trusts, there is no obvious failure signal at the console.

For NERC CIP registered entities this directly stresses CIP-005 electronic security perimeter controls and CIP-012 protection of data in transit between control centers, since the integrity of the remote access channel can no longer be assumed. Under IEC 62443 this undermines the zone and conduit model: the conduit that was supposed to enforce confidentiality and integrity is now a potential interception surface. Pipeline operators governed by TSA SD-02C should map this against their required remote access and network segmentation measures, because a compromised VPN boundary defeats the logical segmentation those directives assume. Water and wastewater utilities working under AWIA 2018 risk assessments should note that remote access to SCADA through this portal class carries a higher residual risk than previously modeled.

Compensating Controls

Do not rely on a vendor patch alone, and do not run active scans against live FortiOS appliances to confirm version, since aggressive probing of edge devices can destabilize VPN sessions and tunnel state. Pull version information from configuration backups and management consoles instead. Immediate measures: restrict the SSL-VPN portal to known source address ranges and move general remote access behind a hardened jump host with independent certificate pinning. Terminate backend sessions at a reverse proxy that enforces strict certificate validation and pins expected backend certificate fingerprints, so a substituted certificate is rejected before it reaches the portal logic. Monitor the path between the portal and internal targets for unexpected certificate changes, TLS downgrade attempts, and new intermediate certificate authorities. A Suricata detection concept: alert on TLS handshakes on the backend leg where the presented certificate issuer or fingerprint does not match a maintained allowlist of expected internal asset certificates, and flag any sudden issuer change for a known internal destination. Treat every such alert as a potential active interception until proven otherwise.

BreachSpider Intel

BreachSpider tracks FortiOS edge exposure and MITM conditions affecting OT remote access boundaries so operators can monitor CVE-2026-121528 and related certificate validation risk without active scanning of production appliances.