In some cases Node.js 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…

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

not scored

EPSS

• CVE-2023-23919: 2.21% estimated exploitation activity in the next 30 days; percentile 82.61 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

In some cases Node.js 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.

Published by the source

29 Nov 2022, 00:00 UTC

Last modified by the source

29 Nov 2022, 00:00 UTC

Source last checked

26 Oct 2026, 16:35 UTC

1. Revision 2 · published · 26 Oct 2026

   Published from vendor_advisory record nodejs-security-wg:core:104

2. Revision 1 · created · 26 Oct 2026

   Created from vendor_advisory record nodejs-security-wg:core:104

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2023-23919

Advisory: In some cases Node.js 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…
IDs: CVE-2023-23919
Record: https://patchnext.com/advisories/cve-2023-23919 (revision 2, source checked 26 Oct 2026, 16:35 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: node 19.2.0, 18.14.1, 16.19.1, 14.21.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- runtime node: affected >= 14.0.0, < 14.21.3; >= 16.0.0, < 16.19.1; >= 18.0.0, < 18.14.1; >= 19.0.0, < 19.2.0; fixed in 18.14.1, 19.2.0, 16.19.1, 14.21.3

## Suggested inspection (read-only)
- runtime node: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on node.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://raw.githubusercontent.com/nodejs/security-wg/main/vuln/core/104.json (Node.js security working group core entry 104 lists CVE-2023-23919 affecting node >=14.0.0 =16.0.0 =18.0.0 =19.0.0 <19.2.0)
- Verified: https://nodejs.org/dist/index.json (The nodejs.org release index dates the first patched release for CVE-2023-23919 to 2022-11-29.)

Commands are suggestions: review each one before running it.