CVE-2021-22930Public exploitNetwork attack vector

Process memory corruption via HTTP/2 stream cancellation

Published Oct 7, 2021 · Updated Apr 30, 2025

Use-after-free in Node.js before 16.6.0, 14.17.4, and 12.22.4 allows remote attackers to corrupt process memory via HTTP/2 cancellation. The native HTTP/2 binding closes and frees a stream reentrantly while nghttp2 is still processing received session data, leaving later callback work to access released memory. The affected path requires an application using HTTP/2 and cancellation during an active stream; demonstrated outcomes include assertion failure, double free, and process crash.

CVSS severity9.8
Critical
EPSS probability36.45%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Use-after-free in Node.js before 16.6.0, 14.17.4, and 12.22.4 allows remote attackers to corrupt process memory via HTTP/2 cancellation. The native HTTP/2 binding closes and frees a stream reentrantly while nghttp2 is still processing received session data, leaving later callback work to access released memory. The affected path requires an application using HTTP/2 and cancellation during an active stream; demonstrated outcomes include assertion failure, double free, and process crash.

The record

CVE
CVE-2021-22930
Published
Oct 7, 2021
Updated
Apr 30, 2025
Vendor
Node.js
Product
Node.js
Classifications
CWE-416, T1499.004
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Oct 7, 2021CVE publishedPublication date reported by the CVE source.
  2. Apr 30, 2025Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=10.0 <10.*
  2. Affected versionversion=11.0 <11.*
  3. Affected versionversion=12.0 <12.22.4
  4. Affected versionversion=13.0 <13.*
  5. Affected versionversion=14.0 <14.17.4
  6. Affected versionversion=15.0 <15.*
  7. Affected versionversion=16.0 <16.6.0
  8. Affected versionversion=4.0 <4.*
  9. Affected versionversion=5.0 <5.*
  10. Affected versionversion=6.0 <6.*
  11. Affected versionversion=7.0 <7.*
  12. Affected versionversion=8.0 <8.*
  13. Affected versionversion=9.0 <9.*

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

Node.js · Node.jsversion=10.0 <10.*; version=11.0 <11.*; version=12.0 <12.22.4; version=13.0 <13.*; version=14.0 <14.17.4; version=15.0 <15.*; version=16.0 <16.6.0; version=4.0 <4.*; version=5.0 <5.*; version=6.0 <6.*; version=7.0 <7.*; version=8.0 <8.*; version=9.0 <9.*

Published CVSS scores

9.8NIST NVDCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
7.5NIST NVDAV:N/AC:L/Au:N/C:P/I:P/A:P

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-416Use After Free
T1499.004Endpoint Denial of Service: Application or System Exploitation

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo