nodejs: GOAWAY HTTP/2 frames cause memory leak outside heap
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| NodeJS | Node | unaffected |
|
No data.
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| Red Hat Enterprise Linux 8 | |||
| nodejs:20-8100020250203134842.489197e6 | cpe:/a:redhat:enterprise_linux:8 | RHSA-2025:1351 | 2025-02-12T00:00:00Z |
| nodejs:18-8100020250207121904.489197e6 | cpe:/a:redhat:enterprise_linux:8 | RHSA-2025:1582 | 2025-02-17T00:00:00Z |
| nodejs:22-8100020250130144944.6d880403 | cpe:/a:redhat:enterprise_linux:8 | RHSA-2025:1611 | 2025-02-17T00:00:00Z |
| Red Hat Enterprise Linux 9 | |||
| nodejs:20-9050020250130114516.rhel9 | cpe:/a:redhat:enterprise_linux:9 | RHSA-2025:1443 | 2025-02-13T00:00:00Z |
| nodejs:18-9050020250206154514.rhel9 | cpe:/a:redhat:enterprise_linux:9 | RHSA-2025:1446 | 2025-02-13T00:00:00Z |
| nodejs:22-9050020250131131518.rhel9 | cpe:/a:redhat:enterprise_linux:9 | RHSA-2025:1613 | 2025-02-17T00:00:00Z |
No data available yet.
| Source | ID | Title |
|---|---|---|
Debian DLA |
DLA-4067-1 | nodejs security update |
Debian DSA |
DSA-6166-1 | nodejs security update |
Debian DSA |
DSA-6272-1 | nodejs security update |
EUVD |
EUVD-2025-3113 | A memory leak could occur when a remote peer abruptly closes the socket without sending a GOAWAY notification. Additionally, if an invalid header was detected by nghttp2, causing the connection to be terminated by the peer, the same leak was triggered. This flaw could lead to increased memory consumption and potential denial of service under certain conditions. This vulnerability affects HTTP/2 Server users on Node.js v18.x, v20.x, v22.x and v23.x. |
No CVSS v4.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: 1.4% (1.367% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
epss
|
epss
|
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:/a:redhat:enterprise_linux:9 |
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Redhat
Redhat enterprise Linux |
|
| CPEs | cpe:/a:redhat:enterprise_linux:8 | |
| Vendors & Products |
Redhat
Redhat enterprise Linux |
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-401 | |
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | No description is available for this CVE. | A memory leak could occur when a remote peer abruptly closes the socket without sending a GOAWAY notification. Additionally, if an invalid header was detected by nghttp2, causing the connection to be terminated by the peer, the same leak was triggered. This flaw could lead to increased memory consumption and potential denial of service under certain conditions. This vulnerability affects HTTP/2 Server users on Node.js v18.x, v20.x, v22.x and v23.x. |
| References |
| |
| Metrics |
cvssV3_0
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | No description is available for this CVE. | |
| Title | nodejs: GOAWAY HTTP/2 frames cause memory leak outside heap | |
| Weaknesses | CWE-400 | |
| References |
| |
| Metrics |
threat_severity
|
cvssV3_1
|