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.
This issue has been addressed in the following products: Red Hat Enterprise Linux 8 Via RHSA-2025:1351 https://access.redhat.com/errata/RHSA-2025:1351
This issue has been addressed in the following products: Red Hat Enterprise Linux 9 Via RHSA-2025:1443 https://access.redhat.com/errata/RHSA-2025:1443
This issue has been addressed in the following products: Red Hat Enterprise Linux 9 Via RHSA-2025:1446 https://access.redhat.com/errata/RHSA-2025:1446
This issue has been addressed in the following products: Red Hat Enterprise Linux 8 Via RHSA-2025:1582 https://access.redhat.com/errata/RHSA-2025:1582
This issue has been addressed in the following products: Red Hat Enterprise Linux 8 Via RHSA-2025:1611 https://access.redhat.com/errata/RHSA-2025:1611
This issue has been addressed in the following products: Red Hat Enterprise Linux 9 Via RHSA-2025:1613 https://access.redhat.com/errata/RHSA-2025:1613