What is the severity of CVE-2025-23085?

CVE-2025-23085 has been classified with a severity that could lead to increased resource consumption due to a memory leak.

How do I fix CVE-2025-23085?

To mitigate CVE-2025-23085, it is recommended to update Node.js to the latest version beyond the vulnerable releases.

Which versions of Node.js are affected by CVE-2025-23085?

CVE-2025-23085 affects Node.js versions from 18.x to 23.x.

What causes the memory leak in CVE-2025-23085?

The memory leak in CVE-2025-23085 is caused when a remote peer abruptly closes the socket without a GOAWAY notification or if invalid headers are detected.

Is there a workaround for CVE-2025-23085?

Currently, the best approach for CVE-2025-23085 is to apply the security updates as there are no effective workarounds identified.

Vulnerability/
CVE-2025-23085

medium

5.3

21/1/2025

7/2/2025

CVE-2025-23085: Node.js security updates: CVE-2025-23083, CVE-2025-23084, CVE-2025-23085

First published: Tue Jan 21 2025(Updated: )

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.

Affected Software	Affected Version	How to fix
Node.js	>=18.x<=23.x

Never miss a vulnerability like this again

Reference Links

https://nodejs.org/en/blog/vulnerability/january-2025-security-releases

Frequently Asked Questions

What is the severity of CVE-2025-23085?
CVE-2025-23085 has been classified with a severity that could lead to increased resource consumption due to a memory leak.
How do I fix CVE-2025-23085?
To mitigate CVE-2025-23085, it is recommended to update Node.js to the latest version beyond the vulnerable releases.
Which versions of Node.js are affected by CVE-2025-23085?
CVE-2025-23085 affects Node.js versions from 18.x to 23.x.
What causes the memory leak in CVE-2025-23085?
The memory leak in CVE-2025-23085 is caused when a remote peer abruptly closes the socket without a GOAWAY notification or if invalid headers are detected.
Is there a workaround for CVE-2025-23085?
Currently, the best approach for CVE-2025-23085 is to apply the security updates as there are no effective workarounds identified.

collector/oss-sec
source/oss-sec
alias/CVE-2025-23083
alias/CVE-2025-23084
alias/CVE-2025-23085
agent/title
agent/first-publish-date
collector/mitre-cve
source/MITRE
agent/references
agent/source
agent/last-modified-date
agent/severity
agent/type
agent/description
agent/trending
agent/event
agent/softwarecombine
agent/tags
agent/guess-ai
agent/software-canonical-lookup
vendor/node.js
canonical/node.js

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2025-23085?
CVE-2025-23085 has been classified with a severity that could lead to increased resource consumption due to a memory leak.
How do I fix CVE-2025-23085?
To mitigate CVE-2025-23085, it is recommended to update Node.js to the latest version beyond the vulnerable releases.
Which versions of Node.js are affected by CVE-2025-23085?
CVE-2025-23085 affects Node.js versions from 18.x to 23.x.
What causes the memory leak in CVE-2025-23085?
The memory leak in CVE-2025-23085 is caused when a remote peer abruptly closes the socket without a GOAWAY notification or if invalid headers are detected.
Is there a workaround for CVE-2025-23085?
Currently, the best approach for CVE-2025-23085 is to apply the security updates as there are no effective workarounds identified.