FortiOS VPN flaw lets attackers intercept portal traffic

Published

Fortinet has patched a high-severity flaw in the FortiOS SSL-VPN web portal that could let a remote, unauthenticated attacker sit in the middle of traffic between the portal and the websites it fetches on a user's behalf. Customers still running FortiOS 7.0 or 6.4 are not getting a fix at all: Fortinet's only remedy for those branches is to migrate to a supported release.

The bug, tracked as CVE-2026-121528 and Fortinet advisory FG-IR-26-193, carries a CVSSv3 score of 7.7. Fortinet classifies it as improper certificate validation (CWE-295), meaning the portal did not properly check the security certificate presented by a backend site. The company says it may allow a man-in-the-middle attack on the communication channel between the SSL-VPN web portal and the backend destination website. The advisory does not describe further exploitation detail.

Not exploited, found in-house

Fortinet lists the flaw as not known to be exploited, and it was discovered internally, credited to John Headley of Fortinet's System Engineering team. No virtual patch is available. The advisory was first published on November 10 and revised on November 12 to explain that the fix behaves differently depending on the FortiOS branch.

That difference matters for administrators. In fixed 7.6 releases, a new setting, remote-https-cert-check, accepts three values: no-check, warn-on-error and reject-on-error. The default is warn-on-error. With reject-on-error, a certificate failure shows a rejection page and the user's only option is to close the connection. In fixed 7.4 and 7.2 releases the check is always on and cannot be changed, and a certificate error brings up a warning page where the user can either accept the risk or close the connection.

SSL-VPN gateways sit on the internet edge, which is why even an internally found, unexploited bug in the component is worth scheduling. See our coverage of Fortinet's critical FortiOS and FortiMail fixes from the same week and the FortiGate configuration leak for recent context.

Upgrade to 7.6.5, 7.4.10 or 7.2.14, or migrate off 7.0 and 6.4

Fortinet recommends following its upgrade path tool when moving between releases. On 7.6, administrators who want a hard stop rather than a warning can set remote-https-cert-check to reject-on-error under config vpn ssl setting, since the default only warns.

For the two older branches the advisory is effectively an end-of-life notice. An organization still running SSL-VPN on 7.0 or 6.4 now has a known, unfixable weakness in the very component that faces the internet, and the only fix is an upgrade it has been putting off.

This briefing is provided by IntelFusions for informational and defensive purposes only. It is based on sources assessed to be reliable at the time of writing, and analytic judgments carry the confidence levels indicated. Indicators of compromise are defanged; re-arm them only in controlled environments. IntelFusions is not affiliated with the organizations named and makes no warranty as to completeness or accuracy.

Read the full analysis on IntelFusions