Automated Threat Modeling

Overview of CVE-2026-121528: FortiOS SSLVPN Web Portal Improper Certificate Validation Enabling Man in the Middle on the Backend Channel

A brief summary of CVE-2026-121528, an improper certificate validation flaw (CWE 295) in the FortiOS SSLVPN web portal that may allow man-in-the-middle interception between the portal and backend websites. Covers affected versions, Fortinet's fixed builds, the new certificate check setting, and detection approaches.

CVE Analysis

9 min read

Gaurav Sarraf
Gaurav Sarraf

2026-11-11

Overview of CVE-2026-121528: FortiOS SSLVPN Web Portal Improper Certificate Validation Enabling Man in the Middle on the Backend Channel

Introduction

Fortinet has fixed a certificate validation flaw in the FortiOS SSLVPN web portal that could let an attacker positioned between a FortiGate and a backend web application read or alter the traffic the portal proxies on a user's behalf. Because the weak link is the FortiGate's own outbound HTTPS session rather than the user's browser connection, the issue is easy to misjudge in both directions: it is not remote code execution, and simply upgrading does not make certificate failures block.

Tracked as CVE-2026-121528 and classified as CWE 295 (Improper Certificate Validation), the issue carries a CVSS v3.1 base score of 8.1 (High) from the Fortinet CNA as listed in NVD. NIST has not yet supplied its own assessment. Fortinet discovered the flaw internally, published advisory FG-IR-26-193 on November 10, 2026, and marks it Known Exploited: No.

Technical Information

Root cause: the portal does not properly verify the backend

Fortinet titles FG-IR-26-193 "SSLVPN Improper Certificate Validation" and names SSLVPN as the affected component. The advisory states that a remote, unauthenticated attacker may perform a man-in-the-middle attack on the communication channel between the SSLVPN web portal and the backend destination website.

In SSLVPN web mode, the FortiGate acts as a reverse proxy: it opens its own HTTPS session to the backend site and passes the content back to the user's browser. If the FortiGate does not properly check the backend server's certificate, someone positioned between the FortiGate and that server can present a fake certificate and read or change the traffic. The browser-to-portal leg is not identified as the affected channel.

Fortinet does not describe the code change in detail, and FortiOS is closed source, so there is no public diff or vulnerable code to show. What we can say is that the fixed builds introduce a backend certificate check setting, which strongly suggests that vulnerable builds did not reliably enforce one.

The CIS bulletin covering this CVE is titled "Multiple Vulnerabilities in Fortinet Products Could Allow for Arbitrary Code Execution" because it bundles several issues. Its specific entry for CVE-2026-121528 is improper certificate validation in SSLVPN, not code execution.

Scoring: three numbers, three contexts

NVD records this CVSS v3.1 base vector:

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
  • AV:N: network attack vector
  • AC:H: high attack complexity
  • PR:N / UI:N: no privileges and no user interaction required
  • S:U: scope unchanged
  • C:H / I:H / A:H: high potential impact to confidentiality, integrity and availability

The published figures differ by source and should keep their labels:

  • NVD (Fortinet CNA): 8.1 High, explicitly a base score.
  • Fortinet advisory: 7.7 High, displayed beside temporal fields E:P/RL:O/RC:C.
  • Tenable plugin 378618: 8.1 base and 7.1 temporal, using E:U/RL:O/RC:C.

CVSS separates intrinsic Base metrics from time-dependent Temporal metrics, so these are not competing assessments. The high-impact ratings describe the scoring model, not observed outcomes such as credential theft or appliance takeover.

Attack flow, as described by the advisory

Based on the advisory and the reverse proxy behavior described above, the scenario looks like this:

  1. A remote user signs in to the FortiGate SSLVPN web portal and requests a backend destination website through it.
  2. The FortiGate initiates its own HTTPS connection to that backend site.
  3. An attacker positioned on the network path between the FortiGate and the backend server intercepts that connection and presents a certificate it controls.
  4. On a vulnerable build, the FortiGate does not properly validate that certificate and continues the session.
  5. The attacker can then read or modify the traffic relayed between the backend site and the user's browser.

What the disclosure does not tell us

The advisory provides no exploit payload, packet sequence, description of the exact verification failure, or demonstrated attack procedure. It also does not explain which conditions drive the High attack complexity rating. We have deliberately not extended the narrative beyond that.

Patch Information

FortiOS is closed source, so the fix ships only as firmware releases documented in FG-IR-26-193 (published November 10, 2026). The advisory lists these fixed builds:

  • FortiOS 7.6: vulnerable 7.6.0 through 7.6.4; fixed in 7.6.5 or later
  • FortiOS 7.4: vulnerable 7.4.0 through 7.4.9; fixed in 7.4.10 or later
  • FortiOS 7.2: vulnerable 7.2.0 through 7.2.13; fixed in 7.2.14 or later
  • FortiOS 8.0: not affected

The fixed builds add a setting that controls how the SSLVPN proxy handles certificate errors from backend servers. The advisory documents it as:

config vpn ssl setting set remote-https-cert-check end

The setting has two modes:

  • warn-on-error (the default): when the backend certificate fails validation, the proxy warns the user instead of silently continuing.
  • reject-on-error: when validation fails, the user sees a rejection page, and per the advisory their "only option is to close the connection."

Upgrading alone does not fully close the gap. With the default warn-on-error, a patched FortiGate notices a bad certificate but still lets the user decide, and users who click through warnings could still connect through an attacker. For strict protection, set remote-https-cert-check to reject-on-error after upgrading. The advisory documents this option only in fixed releases and marks Virtual Patch: No, so it is not a substitute for the upgrade.

Fortinet instructs administrators to follow its recommended upgrade path using its upgrade tool on docs.fortinet.com, rather than assuming a direct jump between arbitrary releases. CIS recommends applying the appropriate Fortinet updates immediately after appropriate testing.

Older branches with no listed fix: the CNA data in NVD also lists FortiOS 7.0.0 through 7.0.19 and 6.4.0 through 6.4.16 as affected, but the advisory's fix table gives no fixed build for either branch. For those systems, remediation means moving to one of the fixed branches above.

Unconfirmed bug ID: the FortiOS 7.6.5 Resolved Issues page does not mention this CVE, FG-IR-26-193, or the new setting, so no internal bug ID for the fix could be confirmed.

Detection Methods

No public sources include exploit signatures, IDS rules, log patterns or IoCs for CVE-2026-121528. Detection today is mostly about finding exposed devices: identify FortiGates running an affected build, then check how they are configured. Health ISAC's bulletin reports no active exploitation in the wild, which is part of why exposure-focused detection matters most right now.

1. Authenticated scanning with Tenable Nessus plugin 378618

Tenable's plugin, titled Fortinet Fortigate SSLVPN Improper Certificate Validation (FG-IR-26-193), maps directly to this CVE.

  • It is a Local check in the Firewalls family (file fortigate_FG-IR-26-193.nasl) and needs the KB items Host/Fortigate/model and Host/Fortigate/version. In practice that means a credentialed scan able to collect model and firmware version.
  • It only compares version numbers. Tenable states that Nessus "has not tested for this issue but has instead relied only on the application's self-reported version number." A finding means the build is vulnerable, not that the device was attacked, and it says nothing about the portal's runtime behavior.
  • Its remediation logic covers the 7.2, 7.4 and 7.6 branches.

2. Manual or CMDB-driven version auditing

Without Nessus, run the same comparison against your asset inventory using the advisory ranges: 7.6.0 through 7.6.4, 7.4.0 through 7.4.9 and 7.2.0 through 7.2.13 affected, 8.0 not affected. Also include 7.0.x and 6.4.x devices, since the NVD affected products table (from Fortinet's CNA record) lists 7.0.0 through 7.0.19 and 6.4.0 through 6.4.16 even though the advisory text only names 7.2 through 7.6. Version-only scanners keyed to the advisory's branch list may not flag those, so check them separately.

Third-party summaries group this CVE with several other FortiOS fixes released the same day, and some list different version ranges for the whole bundle. Use the advisory's ranges for this specific CVE. Finally, confirm whether the SSLVPN web portal is actually enabled on each device, since the vulnerable path only exists when the portal reaches backend websites.

3. Configuration state auditing on patched devices

Because the default is warn-on-error, upgrading does not make certificate failures block. A compliance check or scripted review of config vpn ssl setting across your fleet can find patched devices still on the default. Treat those as only partly covered.

4. Behavioral monitoring for possible interception

No vendor has published exploitation detection content. The advisory does tell you where to look: the intercepted segment is between the FortiGate SSLVPN web portal and the backend website. The following ideas are inferences from the advisory, not published detection logic:

  • If you can observe TLS sessions the FortiGate initiates toward internal or external backend web applications, watch for certificate changes on those connections, such as an unexpected issuer, a self-signed certificate, or a fingerprint that does not match the backend's known certificate.
  • On patched devices left at warn-on-error, user reports of certificate warnings inside the SSLVPN web portal may indicate a failed backend check. Treat those as possible signs of interception worth investigating, not just helpdesk tickets.

No specific log messages, event IDs or IoCs are published for this CVE, so be skeptical of generic "Fortinet MitM" rules marketed for it. Use version and configuration auditing as the main control, with certificate monitoring on the portal-to-backend path as a secondary layer. Rapid7's vulnerability database also has an entry for the CVE that can help with risk correlation, though the page does not describe a specific check.

Affected Systems and Versions

Per Fortinet advisory FG-IR-26-193:

  • FortiOS 7.6.0 through 7.6.4 (fixed in 7.6.5 or later)
  • FortiOS 7.4.0 through 7.4.9 (fixed in 7.4.10 or later)
  • FortiOS 7.2.0 through 7.2.13 (fixed in 7.2.14 or later)
  • FortiOS 8.0: marked not affected; the CVE record solution list includes 8.0.0 or above

Additionally listed as affected in NVD and the machine-readable CVE record, with no in-branch fix identified:

  • FortiOS 7.0.0 through 7.0.19
  • FortiOS 6.4.0 through 6.4.16

Absence from the advisory table should not be read as an unaffected classification for 7.0 or 6.4.

Vulnerable configuration: the exposed path is the SSLVPN web portal connecting to backend destination websites on a user's behalf. On fixed builds, devices left at the default warn-on-error still allow users to proceed past backend certificate failures.

Vendor Security History

John Headley of Fortinet's System Engineering team discovered and reported this flaw internally. Fortinet describes a Secure Product Development Lifecycle built on secure-by-design and secure-by-default principles, including threat modeling, security testing, and internal and independent penetration testing. It reports that approximately 60% of vulnerabilities discovered in 2025 were identified internally, and it publishes advisories on a monthly schedule on the second Tuesday. These are vendor-reported process claims.

For contrast, on April 11, 2025, CISA reported a malicious file associated with previously exploited FortiGate vulnerabilities CVE-2024-21762, CVE-2023-27997 and CVE-2022-42475. The file could permit read-only access to the device filesystem, including configurations, and CISA recommended specific upgrades, configuration review and resetting potentially exposed credentials. That case is part of Fortinet's track record. It is not evidence of exploitation of CVE-2026-121528.

On the threat side for this specific CVE: Fortinet marks it Known Exploited: No, the CIS and Health ISAC bulletins report no exploitation in the wild, and Tenable and VulDB report no known or available exploit. Fortinet's vector uses E:P while Tenable's uses E:U. That difference concerns exploit code maturity, not observed intrusions. No threat actors, campaigns or indicators have been tied to this CVE.

References

Detect & fix
what others miss

Works with
  • GitHub
  • GitLab
  • Bitbucket
  • Azure DevOps Services
  • Gerrit
  • CVS
  • Jira
  • Linear
  • Slack
  • Security Compass
Explore integrations
Security magnifying glass visualization