How severe is CVE-2021-20016?

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

Which packages are affected by CVE-2021-20016?

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

How do I fix CVE-2021-20016?

No fixed version has been published for CVE-2021-20016 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-2021-20016 actively exploited in the wild?

Yes. There are 2 known exploit references for CVE-2021-20016, including 2 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.

Is CVE-2021-20016 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2021-20016 (SonicWall SSLVPN SMA100 SQL Injection Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2021-11-03. CISA required all US federal civilian agencies to remediate this vulnerability by 2021-11-17. 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-2021-20016?

CVE-2021-20016 is classified as SQL Injection (CWE-89). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

Which products and versions are affected by CVE-2021-20016?

CVE-2021-20016 affects sonicwall sma 100 firmware; sonicwall sma 200 firmware; sonicwall sma 210 firmware; sonicwall sma 400 firmware, and 2 more product(s). Check the affected-products list on this page against your deployed version to confirm exposure.

When was CVE-2021-20016 published, and has it been updated?

CVE-2021-20016 was published on February 4, 2021 and was last updated on October 31, 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 2021-11-03 — agencies required to remediate by 2021-11-17 · Ransomware

CVE-2021-20016

CRITICAL

A SQL-Injection vulnerability in the SonicWall SSLVPN SMA100 product allows a remote unauthenticated attacker to perform SQL query to access username password and other session related…

Published

Feb 4, 2021

Updated

Oct 31, 2025

Affected

0 pkgs

Patched

None yet

Exploits

2 known

Description

A SQL-Injection vulnerability in the SonicWall SSLVPN SMA100 product allows a remote unauthenticated attacker to perform SQL query to access username password and other session related information. This vulnerability impacts SMA100 build version 10.x.

Affected Products

6 products · 6 configurations

sma 100 firmwaresonicwall

≥ 10.0.0.0 && < 10.2.0.5-d-29sv

range

sma 200 firmwaresonicwall

all

sma 210 firmwaresonicwall

all

sma 400 firmwaresonicwall

all

sma 410 firmwaresonicwall

all

Application

sma 500vsonicwall

all

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.

A SQL-Injection vulnerability in the SonicWall SSLVPN SMA100 product all…

cisa.govCISANov 2021

A SQL-Injection vulnerability in the SonicWall SSLVPN SMA100 product all…

twitter.comAPIJan 2021

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2021-20016 in your stack?

O3 detects CVE-2021-20016 across dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my stack How O3 SCA works