CVE-2026-33894

CVE-2026-85393 · GHSA-86w9-cpqp-85rv · GHSA-ppp5-5v6c-4jwp · published 26 Mar 2026 · updated 21 Nov 2026

Forge has signature forgery in RSA-PKCS due to ASN.1 extra field

7.5HighCVSS 7.5EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in 1.4.1 and node-forge 1.4.0.

Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript. Prior to version 1.4.0, RSASSA PKCS#1 v1.5 signature verification accepts forged signatures for low public exponent keys (e=3). Attackers can forge signatures by stuffing “garbage” bytes within the ASN structure in order to construct a signature that passes verification, enabling Bleichenbacher style forgery. This issue is similar to CVE-2022-24771, but adds bytes in an addition field within the ASN structure, rather than outside of it. Additionally, forge does not validate that signatures include a minimum of 8 bytes of padding as defined by the specification, providing attackers additional space to construct Bleichenbacher forgeries. Version 1.4.0 patches the issue.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
digitalbazaar<1.4.0, <1.4.11.4.1
npm: node-forge<1.4.0, <=1.4.01.4.0

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in node-forge (npm), strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-33894 severity on Zeptric[![CVE-2026-33894](https://zeptric.io/badge/cve/CVE-2026-33894.svg)](https://zeptric.io/cve/CVE-2026-33894)