How severe is CVE-2022-42475?

CVE-2022-42475 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2022-42475?

Affected package information for CVE-2022-42475 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2022-42475?

No fixed version has been published for CVE-2022-42475 yet. Monitor the advisory for updates, apply mitigations recommended by the vendor, and use O3 Security to track when a fix becomes available in your stack.

Is CVE-2022-42475 actively exploited in the wild?

Yes. There are 12 known exploit references for CVE-2022-42475, including 8 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2022-42475?

CVE-2022-42475 has an EPSS (Exploit Prediction Scoring System) score of 94.0%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

Is CVE-2022-42475 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2022-42475 (Fortinet FortiOS Heap-Based Buffer Overflow Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2022-12-13. CISA required all US federal civilian agencies to remediate this vulnerability by 2023-01-03. The required action was: Apply updates per vendor instructions. This CVE has been used in known ransomware campaigns. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2022-42475?

CVE-2022-42475 is classified as CWE-197 (CWE-197), Out-of-bounds Write (CWE-787). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Which products and versions are affected by CVE-2022-42475?

CVE-2022-42475 affects fortinet fortios; fortinet fortiproxy. Check the affected-products list on this page against your deployed version to confirm exposure.

When was CVE-2022-42475 published, and has it been updated?

CVE-2022-42475 was published on January 2, 2023 and was last updated on October 24, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CISA KEV·Added 2022-12-13 — agencies required to remediate by 2023-01-03 · Ransomware

CVE-2022-42475

CRITICAL

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…

Published

Jan 2, 2023

Updated

Oct 24, 2025

Affected

0 pkgs

Patched

None yet

Exploits

12 known

EPSS Exploitation Probability

via FIRST.org ↗

94.0%probability of exploitation in next 30 days

Very High Risk100th percentile0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Description

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 Products

2 products · 19 configurations

fortiosfortinet

≥ 7.0.0 && ≤ 5.6.14

range

Application

fortiproxyfortinet

≥ 7.2.0 && ≤ 1.2.13

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.