p PatchFirst

CVE-2025-23085

CVE-2025-23085

This page contains facts from public vulnerability sources. Check the original advisory before updating.

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.

CVSS 5.3 · Medium · EPSS 1.4% · Fix available

Published
Updated

Stack: system · node

Affected products and versions

  • node.js

    Versions
    • ≥ 4.0, < 4.*: Affected (semver)
    • ≥ 5.0, < 5.*: Affected (semver)
    • ≥ 6.0, < 6.*: Affected (semver)
    • ≥ 7.0, < 7.*: Affected (semver)
    • ≥ 8.0, < 8.*: Affected (semver)
    • ≥ 9.0, < 9.*: Affected (semver)
    • ≥ 10.0, < 10.*: Affected (semver)
    • ≥ 11.0, < 11.*: Affected (semver)
    • ≥ 12.0, < 12.*: Affected (semver)
    • ≥ 13.0, < 13.*: Affected (semver)
    • ≥ 14.0, < 14.*: Affected (semver)
    • ≥ 15.0, < 15.*: Affected (semver)
    • ≥ 16.0, < 16.*: Affected (semver)
    • ≥ 17.0, < 17.*: Affected (semver)
    • ≥ 18.0, < 18.20.6: Affected (semver)
    • ≥ 19.0, < 19.*: Affected (semver)
    • ≥ 20.0, < 20.18.2: Affected (semver)
    • ≥ 21.0, < 21.*: Affected (semver)
    • ≥ 22.0, < 22.13.1: Affected (semver)
    • ≥ 23.0, < 23.6.1: Affected (semver)

    Update to 18.20.6; Update to 20.18.2; Update to 22.13.1; Update to 23.6.1

  • nodejs Debian:12

    Versions
    • 18.13.0+dfsg1-1
    • 18.13.0+dfsg1-1.1
    • 18.19.0+dfsg-1
    • 18.19.0+dfsg-2
    • 18.19.0+dfsg-3
    • 18.19.0+dfsg-4
    • 18.19.0+dfsg-5
    • 18.19.0+dfsg-6
    • 18.19.0+dfsg-6~deb12u1
    • 18.19.0+dfsg-6~deb12u2
    • 18.19.1+dfsg-1
    • 18.19.1+dfsg-2
    • 18.19.1+dfsg-3
    • 18.19.1+dfsg-3.1
    • 18.19.1+dfsg-4
    • 18.19.1+dfsg-6
    • 18.20.1+dfsg-1
    • 18.20.1+dfsg-2
    • 18.20.1+dfsg-3
    • 18.20.1+dfsg-4
    • 18.20.4+dfsg-1~deb12u1
    Affected ranges
    • ECOSYSTEM: < 18.20.4+dfsg-1~deb12u2

    Update to 18.20.4+dfsg-1~deb12u2

  • nodejs Debian:13

    Versions
    • 20.19.2+dfsg-1
    Affected ranges
    • ECOSYSTEM: < 20.19.2+dfsg-1+deb13u1

    Update to 20.19.2+dfsg-1+deb13u1

  • nodejs Debian:14

    Affected ranges
    • ECOSYSTEM: < 20.18.2+dfsg-1

    Update to 20.18.2+dfsg-1

  • nodejs Ubuntu:Pro:20.04:LTS

    Versions
    • 10.15.2~dfsg-2ubuntu1
    • 10.17.0~dfsg-2ubuntu4
    • 10.17.0~dfsg-2ubuntu6
    • 10.19.0~dfsg-3ubuntu1
    • 10.19.0~dfsg-3ubuntu1.1
    • 10.19.0~dfsg-3ubuntu1.2
    • 10.19.0~dfsg-3ubuntu1.3
    • 10.19.0~dfsg-3ubuntu1.5
    • 10.19.0~dfsg-3ubuntu1.6
    • 10.19.0~dfsg-3ubuntu1.6+esm2
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • nodejs Ubuntu:Pro:22.04:LTS

    Versions
    • 12.22.5~dfsg-5ubuntu1
    • 12.22.7~dfsg-2ubuntu1
    • 12.22.7~dfsg-2ubuntu3
    • 12.22.9~dfsg-1ubuntu2
    • 12.22.9~dfsg-1ubuntu3
    • 12.22.9~dfsg-1ubuntu3.1
    • 12.22.9~dfsg-1ubuntu3.2
    • 12.22.9~dfsg-1ubuntu3.3
    • 12.22.9~dfsg-1ubuntu3.4
    • 12.22.9~dfsg-1ubuntu3.5
    • 12.22.9~dfsg-1ubuntu3.6
    • 12.22.9~dfsg-1ubuntu3.6+esm2
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • nodejs Ubuntu:24.04:LTS

    Versions
    • 18.13.0+dfsg1-1ubuntu2
    • 18.19.1+dfsg-2ubuntu4
    • 18.19.1+dfsg-6ubuntu1
    • 18.19.1+dfsg-6ubuntu2
    • 18.19.1+dfsg-6ubuntu5
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

Original sources

Check your server →