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.
CVE-2022-42475
Score elevated to 9.8 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2022-12-13), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 9.8 retained for reference. Confidence: HIGH.
- 9 internet-facing services (distinct ip:port) on record running an affected version — derived from Shodan data (© Shodan); a patched service can stay counted while its port stays open
- Actively exploited in the wild (CISA-KEV)
- Linked to ransomware campaigns
No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.
9 internet-facing services (distinct ip:port) on record running a version that maps to CVE-2022-42475, in our KEV-Exposure radar’s Shodan-derived sample.
How it counts: every 12 hours, when Shodan query credits allow, the radar runs one Shodan query per tracked product, reads up to 100 ip:port services per query, and keeps a service when its banner version matches a CISA-KEV or high-EPSS CVE; a service is dropped when neither a search nor a Shodan InternetDB port re-check has refreshed it for 21 days. A re-check that finds the port still listed by Shodan InternetDB refreshes the service without re-reading the banner, so a patched service can stay counted while its port stays open. A count is a banner-version inference over a sample, not an exploit test and not an internet-wide census, and the unit is a service, not a machine: a machine answering on two ports counts twice.
- CVSS v3
- 9.8
- EG Score
- 9.8CRITICALhigh confidence
- EG Risk
- 99EG Risk 99/100CISA SSVC
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity98% × 45%Exploitation100% × 40%Automatability100% × 15%CISA SSVC: Attend at low mission impact; Act at medium or high.Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation sooner than your standard update timelines at low mission impact and as soon as possible at medium or high, and watch the vendor's advisory for the fix. - EPSS PROB
- 99%
- EPSS %ILE
- 99th
- KEV
- ⚠ Exploited
CISA SSVCAttend at low mission impact; Act at medium or high.
No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation sooner than your standard update timelines at low mission impact and as soon as possible at medium or high, and watch the vendor's advisory for the fix.
Exploitation active (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table
Published
January 2, 2023
Last Modified
October 24, 2025
Advisory Details (2)
Auto-updated Oct 9, 2026Known Exploited Vulnerabilities Catalog | CISA
Known Exploited Vulnerabilities Catalog | CISA. Listed in CISA Known Exploited Vulnerabilities catalog.
https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2022-42475Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 43× in last 7d / 202× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 898 total refreshes for this CVE.
- 2026-10-10 01:55 UTCGHSA enrichment
- 2026-10-09 22:00 UTCGHSA enrichment
- 2026-10-09 18:04 UTCGHSA enrichment
- 2026-10-09 14:10 UTCGHSA enrichment
- 2026-10-09 10:16 UTCGHSA enrichment
- 2026-10-09 06:23 UTCGHSA enrichment
- 2026-10-09 02:28 UTCGHSA enrichment
- 2026-10-08 22:34 UTCGHSA enrichment
- 2026-10-08 18:40 UTCGHSA enrichment
- 2026-10-08 14:46 UTCGHSA enrichment
- 2026-10-08 10:52 UTCGHSA enrichment
- 2026-10-08 06:57 UTCGHSA enrichment
- 2026-10-08 03:03 UTCGHSA enrichment
- 2026-10-07 23:09 UTCGHSA enrichment
- 2026-10-07 19:14 UTCGHSA enrichment
- 2026-10-07 15:20 UTCGHSA enrichment
- 2026-10-07 11:26 UTCGHSA enrichment
- 2026-10-07 07:32 UTCGHSA enrichment
- 2026-10-07 03:37 UTCGHSA enrichment
- 2026-10-06 23:42 UTCGHSA enrichment
- 2026-10-06 19:48 UTCGHSA enrichment
- 2026-10-06 15:54 UTCGHSA enrichment
- 2026-10-06 12:00 UTCGHSA enrichment
- 2026-10-06 08:06 UTCGHSA enrichment
- 2026-10-06 04:13 UTCGHSA enrichment
Show 75 moreShow fewer
- 2026-10-06 00:19 UTCGHSA enrichment
- 2026-10-05 20:24 UTCGHSA enrichment
- 2026-10-05 16:30 UTCGHSA enrichment
- 2026-10-05 12:36 UTCGHSA enrichment
- 2026-10-05 08:43 UTCGHSA enrichment
- 2026-10-05 04:49 UTCGHSA enrichment
- 2026-10-05 00:54 UTCGHSA enrichment
- 2026-10-04 20:59 UTCGHSA enrichment
- 2026-10-04 17:04 UTCGHSA enrichment
- 2026-10-04 13:10 UTCGHSA enrichment
- 2026-10-04 09:16 UTCGHSA enrichment
- 2026-10-04 05:22 UTCGHSA enrichment
- 2026-10-04 01:28 UTCGHSA enrichment
- 2026-10-03 21:34 UTCGHSA enrichment
- 2026-10-03 17:39 UTCGHSA enrichment
- 2026-10-03 13:45 UTCGHSA enrichment
- 2026-10-03 09:49 UTCGHSA enrichment
- 2026-10-03 05:55 UTCGHSA enrichment
- 2026-10-03 02:01 UTCGHSA enrichment
- 2026-10-02 22:07 UTCGHSA enrichment
- 2026-10-02 18:14 UTCGHSA enrichment
- 2026-10-02 14:18 UTCGHSA enrichment
- 2026-10-02 10:24 UTCGHSA enrichment
- 2026-10-02 06:30 UTCGHSA enrichment
- 2026-10-02 02:36 UTCGHSA enrichment
- 2026-10-01 22:38 UTCGHSA enrichment
- 2026-10-01 18:44 UTCGHSA enrichment
- 2026-10-01 14:48 UTCGHSA enrichment
- 2026-10-01 10:54 UTCGHSA enrichment
- 2026-10-01 07:00 UTCGHSA enrichment
- 2026-10-01 03:06 UTCGHSA enrichment
- 2026-09-30 23:12 UTCGHSA enrichment
- 2026-09-30 19:18 UTCGHSA enrichment
- 2026-09-30 15:24 UTCGHSA enrichment
- 2026-09-30 11:30 UTCGHSA enrichment
- 2026-09-30 07:36 UTCGHSA enrichment
- 2026-09-30 03:42 UTCGHSA enrichment
- 2026-09-29 23:48 UTCGHSA enrichment
- 2026-09-29 19:54 UTCGHSA enrichment
- 2026-09-29 15:58 UTCGHSA enrichment
- 2026-09-29 12:04 UTCGHSA enrichment
- 2026-09-29 08:10 UTCGHSA enrichment
- 2026-09-29 04:15 UTCGHSA enrichment
- 2026-09-29 00:21 UTCEG score recompute
- 2026-09-29 00:20 UTCGHSA enrichment
- 2026-09-28 20:27 UTCGHSA enrichment
- 2026-09-28 16:33 UTCGHSA enrichment
- 2026-09-28 12:38 UTCGHSA enrichment
- 2026-09-28 08:44 UTCGHSA enrichment
- 2026-09-28 04:50 UTCGHSA enrichment
- 2026-09-28 00:56 UTCGHSA enrichment
- 2026-09-27 21:51 UTCCISA KEV update
- 2026-09-27 21:02 UTCGHSA enrichment
- 2026-09-27 17:08 UTCGHSA enrichment
- 2026-09-27 13:15 UTCGHSA enrichment
- 2026-09-27 09:21 UTCGHSA enrichment
- 2026-09-27 05:28 UTCGHSA enrichment
- 2026-09-27 01:32 UTCGHSA enrichment
- 2026-09-26 21:38 UTCGHSA enrichment
- 2026-09-26 17:45 UTCGHSA enrichment
- 2026-09-26 13:50 UTCGHSA enrichment
- 2026-09-26 09:55 UTCGHSA enrichment
- 2026-09-26 06:00 UTCGHSA enrichment
- 2026-09-26 02:03 UTCGHSA enrichment
- 2026-09-25 22:09 UTCGHSA enrichment
- 2026-09-25 19:35 UTCCISA KEV update
- 2026-09-25 18:15 UTCGHSA enrichment
- 2026-09-25 14:55 UTCCISA KEV update
- 2026-09-25 14:21 UTCGHSA enrichment
- 2026-09-25 10:25 UTCGHSA enrichment
- 2026-09-25 06:31 UTCGHSA enrichment
- 2026-09-25 02:38 UTCGHSA enrichment
- 2026-09-24 22:44 UTCGHSA enrichment
- 2026-09-24 19:31 UTCCISA KEV update
- 2026-09-24 18:50 UTCGHSA enrichment
Publicly available exploits
(4 references)Working exploit code is in the public domain (4 GitHub PoCs). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.
- GitHub PoC0xhaggis/CVE-2022-42475First seen Jun 21, 2023
An exploit for CVE-2022-42475, a pre-authentication heap overflow in Fortinet networking products
Open source ↗ - GitHub PoCP4x1s/CVE-2022-42475-RCE-POCFirst seen Mar 23, 2023
CVE-2022-42475 飞塔RCE漏洞 POC
Open source ↗ - GitHub PoCAmir-hy/cve-2022-42475First seen Mar 16, 2023
FortiOS buffer overflow vulnerability
Open source ↗ - GitHub PoCscrt/cve-2022-42475First seen Feb 23, 2023
POC code to exploit the Heap overflow in Fortinet's SSLVPN daemon
Open source ↗
Related CVEs(same CWE)
Frequently asked(6)
What is CVE-2022-42475?
When was CVE-2022-42475 disclosed?
Is CVE-2022-42475 actively exploited?
What is the CVSS score of CVE-2022-42475?
Which products are affected by CVE-2022-42475?
How do I remediate CVE-2022-42475?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2022-42475
Is Your Infrastructure Affected by CVE-2022-42475?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.