7.5
High
CVE-2023-23919 A cryptographic vulnerability exists in…
Description
A cryptographic vulnerability exists in Node.js <19.2.0, <18.14.1, <16.19.1, <14.21.3 that in some cases did does not clear the OpenSSL error stack after operations that may set it. This may lead to false positive errors during subsequent cryptographic operations that happen to be on the same thread. This in turn could be used to cause a denial of service.
Affected products and versions
| Product | Affected versions | Fixed in |
|---|---|---|
| Node 19.0 | 19.0 → < 19.2.0 | 19.2.0 |
| Node 18.0 | 18.0 → < 18.14.1 | 18.14.1 |
| Node 17.0 | 17.0 → latest | No fix stated |
| Node 16.0 | 16.0 → < 16.19.1 | 16.19.1 |
| Node 15.0 | 15.0 → latest | No fix stated |
| Node 14.0 | 14.0 → < 14.21.3 | 14.21.3 |
| Node 13.0 | 13.0 → latest | No fix stated |
| Node 12.0 | 12.0 → latest | No fix stated |
| Node 11.0 | 11.0 → latest | No fix stated |
Show the 7 other branches Hide the 7 other branches
Other CVEs of Node
The 129 CVEs of Node →
CVE-2026-106074
A flaw in Node.js `crypto` causes the internal entropy caches used by `crypto.randomUUID()`, `crypto.randomUUIDv7()`,…
4.8
Medium
CVE-2026-106073
A flaw in Node.js Permission Model filesystem enforcement leaves `fs.realpathSync()` without the required read…
3.3
Low
CVE-2026-105482
A flaw in Node.js DNS resolution allows hostnames containing a NUL byte to be silently truncated by the dns.resolve*()…
7.4
High
CVE-2026-106072
A flaw in Node.js TLS hostname verification allows a certificate with only a DNS SAN to authenticate an IP endpoint when…
6.7
Medium