Actively exploitedKnown ransomware use

CVE-2022-42475 Fortinet FortiOS Heap-Based Buffer Overflow Vulnerability

Multiple versions of Fortinet FortiOS SSL-VPN contain a heap-based buffer overflow vulnerability which can allow an unauthenticated, remote attacker to execute arbitrary code or commands via specifically crafted requests.

From the CISA KEV catalogue version 2026.11.06, with Cybergen analysis. Updated 6 Nov 2026.

Our Assessment

Should You Worry?

Patch nowCybergen assessment
  • CISA confirmed exploitation in the wild and added it to the Known Exploited Vulnerabilities catalogue on 13 Dec 2022.
  • CISA lists it as known to be used in ransomware campaigns.
  • Rated Critical severity (CVSS 9.3, scored by Vendor).
  • This product type is often exposed to the internet, which is where attackers scan for it first.
  • Named in Cybergen threat actor reporting: Volt Typhoon.
  • It has been in the catalogue for 1,424 days. Systems still unpatched now have almost certainly been scanned for it.
The Vulnerability

What It Is

A heap-based buffer overflow vulnerability [CWE-122] in FortiOS SSL-VPN 7.2.0 through 7.2.2, 7.0.0 through 7.0.8, 6.4.0 through 6.4.10, 6.2.0 through 6.2.11, 6.0.15 and earlier and FortiProxy SSL-VPN 7.2.0 through 7.2.1, 7.0.7 and earlier may allow a remote unauthenticated attacker to execute arbitrary code or commands via specifically crafted requests.

Affected Versions

ProductVersions
Fortinet FortiProxy7.2.0 to 7.2.1
7.0.0 to 7.0.7
2.0.0 to 2.0.11
1.2.0 to 1.2.13
1.1.0 to 1.1.6
1.0.0 to 1.0.7
Fortinet FortiOS7.2.0 to 7.2.2
7.0.0 to 7.0.8
6.4.0 to 6.4.10
6.2.0 to 6.2.11
6.0.0 to 6.0.15
5.6.0 to 5.6.14

From the public CVE record, as supplied by the vendor. Always confirm against the vendor advisory.

From Watch to Action

What To Do Now

  1. 1

    Find it

    Search your asset inventory and external attack surface for Fortinet FortiOS. Include cloud images, appliances and anything a supplier runs for you.

    Attack Surface Management
  2. 2

    Fix it

    Apply updates per vendor instructions.

    Vulnerability Management
  3. 3

    Hunt for compromise

    If an affected system was reachable before you patched, assume it may have been hit. Check logs, new accounts, web shells and outbound connections from the date of exposure.

    Incident Response
  4. 4

    Prove it is fixed

    Rescan or test the system after patching. Upgrades that fail silently and forgotten secondary instances are common.

    Penetration Testing

Not Sure If You Are Exposed?

Our attack surface and vulnerability teams can check your internet-facing estate for CVE-2022-42475 and every other exploited flaw on the list.

Check My Exposure