CVE-2023-23919: A cryptographic vulnerability exists in Node.js <19.2.0, <18.14.1, <16.19.1, <14.21.3 that in some cases did d

Q: How urgent is CVE-2023-23919?

Priority 57/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action

This week

HIGH 7.5REMOTEUPGRADE

CVE-2023-23919 is a high-severity flaw (CVSS 7.5) affecting node.js. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

High severity
Public exploit reference
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	2.2% (top 18%)
CISA exploited list	No
Weakness	CWE-310
Published	2023-02-23
Last modified	2026-10-24

Publisher (CNA): HackerOne · Vendor: nodejs

Last updated 2026-10-24 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2023-02-23 20:15 UTCPublished CVE record published
2026-10-24 13:10 UTCUpdated Record last modified

nodejs node.js UPGRADE

Affected: >= 14.0.0 and <= 14.14.0 · >= 14.0.0 and < 14.21.3 · >= 16.0.0 and <= 16.12.0 · >= 16.0.0 and < 16.19.1 · >= 18.0.0 and <= 18.11.0 · >= 18.0.0 and < 18.14.1 · >= 19.0.0 and < 19.2.0

Fixed in: 14.21.3, 16.19.1, 18.14.1, 19.2.0

Safe to downgrade to: a release before 14.0.0

1. Check installed version

apt-cache policy node.js || rpm -q node.js || node.js --version

2. UPGRADE to 14.21.3 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade node.js

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade node.js

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 14.0.0 (Debian / Ubuntu)

apt-cache madison node.js sudo apt install node.js=<VERSION_BEFORE_14.0.0> sudo apt-mark hold node.js

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list node.js sudo dnf downgrade node.js-<VERSION_BEFORE_14.0.0> sudo dnf versionlock add node.js

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Exact fixes by distribution

Fedora 46 · gnome-shell-extension-tiling-assistant · FIXED · 56-1.fc46 · FEDORA-2026-ebf66a5321 · source

sudo dnf upgrade --advisory=FEDORA-2026-ebf66a5321

Ubuntu 20.04 · nodejs · NOT AFFECTED

Ubuntu 22.04 · nodejs · NOT AFFECTED

Ubuntu 24.04 · nodejs · NOT AFFECTED

Debian 12 · nodejs · FIXED · 18.19.0+dfsg-6~deb12u1

sudo apt update && sudo apt install --only-upgrade nodejs dpkg --compare-versions "$(dpkg-query -W -f='${Version}' nodejs)" ge "18.19.0+dfsg-6~deb12u1" && echo PATCHED || echo STILL-VULNERABLE

Debian 13 · nodejs · FIXED · 18.13.0+dfsg1-1.1

sudo apt update && sudo apt install --only-upgrade nodejs dpkg --compare-versions "$(dpkg-query -W -f='${Version}' nodejs)" ge "18.13.0+dfsg1-1.1" && echo PATCHED || echo STILL-VULNERABLE

Alpine 3.20 · nodejs · FIXED · nodejs-18.14.1-r0

apk add --upgrade nodejs apk info -v nodejs

Alpine 3.21 · nodejs · FIXED · nodejs-18.14.1-r0

apk add --upgrade nodejs apk info -v nodejs

Alpine 3.22 · nodejs · FIXED · nodejs-18.14.1-r0

apk add --upgrade nodejs apk info -v nodejs

Alpine 3.23 · nodejs · FIXED · nodejs-18.14.1-r0

apk add --upgrade nodejs apk info -v nodejs

Amazon Linux 2023 · see advisory · FIXED · ALAS2023-2023-226 · source

sudo dnf update --advisory=ALAS2023-2023-226

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2023-23919?

node.js: upgrade to 14.21.3, 16.19.1, 18.14.1, 19.2.0. Exact commands for each OS are on this page.

Is CVE-2023-23919 being exploited?

CVE-2023-23919 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2023-23919 affect?

CVE-2023-23919 affects node.js. Severity is high (CVSS 7.5). 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 c

How urgent is CVE-2023-23919?

Priority 57/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action

Software pages

Node.js vulnerabilities · OpenSSL vulnerabilities

Related CVEs

CVE-2023-23918 HIGH 7.5 UPGRADE A privilege escalation vulnerability exists in Node.js <19.6.1, <18.14.1, <16.19.1 and <14.21.3 that made it p
CVE-2026-58043 HIGH 8.4 UPGRADE A flaw in Node.js Permission Model enforcement can over-grant filesystem access across radix-tree prefix bound
CVE-2026-56847 MEDIUM 6.1 UPGRADE A flaw in Node.js Permission Model enforcement allows `trace_events.createTracing().enable()` Writes Trace Log
CVE-2026-56850 MEDIUM 4.4 UPGRADE A flaw in Node.js HTTPS Agent connection reuse can cause PFX object-array key collisions, allowing mutual TLS

References

← Back to latest CVEs