REDHAT-BUG-2452458: High severity npm/node-forge vulnerability

Q: What certificate-chain condition is required for exploitation?

An intermediate certificate must lack both the basicConstraints and keyUsage extensions. In affected versions, node-forge can then accept a leaf certificate without these extensions as a CA capable of signing additional certificates.

Q: Which versions address this issue?

Version 1.4.0 patches the issue. Versions prior to 1.4.0 are described as not enforcing the relevant RFC 5280 basicConstraints requirements.

Published Mar 27, 2026

Updated

Forge (also called node-forge) is a native implementation of Transport Layer Security in JavaScript. Prior to version 1.4.0, pki.verifyCertificateChain() does not enforce RFC 5280 basicConstraints requirements when an intermediate certificate lacks both the basicConstraints and keyUsage extensions. This allows any leaf certificate (without these extensions) to act as a CA and sign other certificates, which node-forge will accept as valid. Version 1.4.0 patches the issue.

Affected Software

1 affected component

npm/node-forge<1.4.0

Event History

Mar 27, 2026

Data Sourced

via Red Hat·09:02 PM

DescriptionSeverityAffected Software

Frequently Asked Questions

What certificate-chain condition is required for exploitation?

An intermediate certificate must lack both the basicConstraints and keyUsage extensions. In affected versions, node-forge can then accept a leaf certificate without these extensions as a CA capable of signing additional certificates.

Which versions address this issue?

Version 1.4.0 patches the issue. Versions prior to 1.4.0 are described as not enforcing the relevant RFC 5280 basicConstraints requirements.