CVE-2021-22940
No exploitation reported by the sources we read.
- Published2021-08-16
- Fixed in16.6.2 · 14.17.5 · 12.22.5
- WeaknessCWE-416
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
Node.js before 16.6.1, 14.17.5, and 12.22.5 is vulnerable to a use after free attack where an attacker might be able to exploit the memory corruption, to change process behavior.
Timeline
dates in UTC- 2021-08-1619:15CVE publishedNVD
- 2026-10-2319:23EPSS crossed 10 %FIRST EPSS
Observed activity
isMalicious corpus · updated 2026-10-23 21:37 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2021-22940?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2021-22940?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD · OSV| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 16.x | ≥ 16.0.0, < 16.6.2 | 16.6.2 | NVD · OSV |
| 14.x | ≥ 14.0.0, < 14.17.5 | 14.17.5 | NVD · OSV |
| 12.x | ≥ 12.0.0, < 12.22.5 | 12.22.5 | NVD · OSV |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 8.57 | = 8.57 | no fix published | NVD |
| 8.58 | = 8.58 | no fix published | NVD |
| 8.59 | = 8.59 | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 20.3 | = 20.3.3 | no fix published | NVD |
| 21.2 | = 21.2.0 | no fix published | NVD |
4 more products in the sources.
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Distribution builds and vendor advisories
Packages from OSV.dev and products from the vendors' CSAF advisories.
version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.
Packages
- nodejsAlmaLinux:8all versions · fixed in 1:12.22.5-1.module_el8.4.0+2529+af52a4c7and 3 other packages
- nodejsAlmaLinux:8all versions · fixed in 1:12.22.5-1.module_el8.5.0+85+79a7b441and 2 other packages
- nodejs-nodemonAlmaLinux:8all versions · fixed in 2.0.3-1.module_el8.4.0+2521+c668cc9f
- nodejs-packagingAlmaLinux:8all versions · fixed in 17-3.module_el8.3.0+2023+d2377ea3
- nodejs-packagingAlmaLinux:8all versions · fixed in 17-3.module_el8.4.0+2224+b07ac28e
- nodejs-packagingAlmaLinux:8all versions · fixed in 17-3.module_el8.4.0+2521+c668cc9f
- nodejs-packagingAlmaLinux:8all versions · fixed in 23-3.module_el8.4.0+2522+3bd42762
- nodejs-packagingAlmaLinux:8all versions · fixed in 23-3.module_el8.5.0+254+b4526b16
2 more package ranges on OSV.dev
Fix
- Update Node.js to 16.6.2 · 14.17.5 · 12.22.5
Advisories and patches
- cert-portal.siemens.comPatch
- nodejs.orgPatch · Vendor Advisory
- www.oracle.comPatch
- www.oracle.comPatch
- www.oracle.comPatch
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- none listed PoC-in-GitHub
Sources
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
- Published
- 2021-08-16
- Last Modified
- 2026-06-17
- NVD status
- Modified
Frequently asked questions
What is CVE-2021-22940?
Is CVE-2021-22940 actively exploited?
What is the CVSS score for CVE-2021-22940?
Running Node.js? Hear about its next vulnerability
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.