Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
A recurring series of pre-authentication flaws in FortiOS SSL-VPN has given attackers credentials and remote code execution on perimeter devices since 2018, with several exploited as zero-days.

What Are the Fortinet SSL-VPN Vulnerabilities?
Fortinet’s FortiGate appliances terminate SSL-VPN connections for a very large number of organisations, which makes FortiOS one of the most valuable targets available to an attacker. Since 2018 a series of pre-authentication vulnerabilities in that SSL-VPN component has provided credential theft, authentication bypass, and remote code execution on the device itself — the point in the network where an attacker most wants to be.
These are not a single flaw. They are a pattern, and the pattern includes slow patching, long-lived credentials that survive the fix, and repeated use by both state-aligned and criminal operators.
sslvpn_websession files containing plaintext usernames and passwords. Patched in May 2019. In November 2020 a list of roughly 50,000 vulnerable devices was published, followed by a dump of credentials harvested from them. It has remained on CISA’s most-exploited lists for years, and the NCSC and CISA jointly attributed its use to Russian SVR operators in 2021.sslvpnd giving pre-authentication remote code execution. Disclosed in December 2022 after being exploited as a zero-day, with a custom implant that patched FortiOS logging processes to hide the intrusion.Separately, in January 2025 a group calling itself the Belsen Group published configuration files and VPN credentials for around 15,000 FortiGate devices, harvested some years earlier through CVE-2022-40684. Many of those credentials were still valid.
Three reasons, and all three are about process rather than technology.
First, credentials stolen through CVE-2018-13379 remained valid long after the patch, because organisations applied the firmware update and did not reset user passwords. The vulnerability was closed; the access was not.
Second, edge appliances sit outside normal patch management. They are not in the server estate, they are not in the workstation estate, and patching them requires a maintenance window that affects every remote worker. The result is firmware that is years behind.
Third, appliances are rarely monitored. There is no endpoint agent on a FortiGate, local logs are limited, and several intrusions specifically tampered with logging. A compromise can sit there indefinitely.
Our infrastructure security testing services include perimeter appliance review and compromise assessment, which answers the version question and the harder question at the same time.
They are internet-facing by necessity, they hold or validate credentials, they sit at the boundary between untrusted and internal networks, and they cannot run an endpoint agent. A compromise provides access that looks like legitimate remote working. Add infrequent patching and limited logging, and they become one of the most productive initial access routes available.
No. The vulnerability exposed plaintext usernames and passwords, and those credentials stayed valid after the firmware update unless they were changed. Many organisations were compromised months or years later using credentials harvested before they patched. Any exposure to that flaw requires a full credential reset for VPN users and administrators.
It protects against stolen passwords, which is a large share of the risk and worth enforcing. It does not protect against vulnerabilities that bypass authentication or achieve code execution before any authentication occurs, which describes several of the FortiOS issues. Layer it with prompt patching, restricted management access, logging, and segmentation behind the VPN.
Compare the running configuration against a known-good baseline, looking for unexpected administrator accounts, modified admin profiles, trusted host changes, new automation or scripts, and altered logging settings. Review centrally held logs for logins from unusual locations and for configuration changes outside change windows. Engage specialist responders if you find discrepancies.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.