A memory leak in Node.js’s OpenSSL integration occurs when converting `X.509` certificate fields to UTF-8 without freeing the allocated buffer. When applications call `socket.getPeerCertificate(true)`, each certificate field leaks memory, allowing remote clients to trigger steady memory growth through repeated TLS connections. Over time this can lead to resource exhaustion and denial of service.
| Product | Vendor Advisory | Solution File | Added | Published |
|---|---|---|---|---|
| Amazon_linux_2023 | — | Upgrade nodejs24-libs-debuginfoUpgrade nodejs24-npmUpgrade nodejs24-libsUpgrade nodejs24Upgrade nodejs24-develUpgrade v8-13.6-develUpgrade nodejs24-debuginfoUpgrade nodejs24-docsUpgrade nodejs24-debugsourceUpgrade nodejs24-full-i18n | Feb 10, 2026 | Jan 20, 2026 |
| Redhat_linux | — | No solution exists | Jul 17, 2026 | Jan 20, 2026 |
With curated Threat Intelligence, you can see which vulnerabilities truly put you at risk, prioritize what matters most, and act before attackers do.
Explore Intelligence Hub