Answer in brief
CVE-2026-85393 records a High severity (CVSS 7.5) vulnerability in Forge has signature forgery in RSA-PKCS due to ASN.1 extra field. The current sources do not mark it as known exploited. The current feed maps digitalbazaar/forge (generic), digitalbazaar/forge (generic), node-forge (npm), node-forge (npm) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps digitalbazaar/forge (generic), digitalbazaar/forge (generic), node-forge (npm), node-forge (npm) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| digitalbazaar/forgegeneric | <1.4.0 | 1.4.0 |
| digitalbazaar/forgegeneric | 0 | Not reported |
| node-forgenpm | <=1.4.0 | Not reported |
| node-forgenpm | >=0 | Not reported |
| node-forgenpm | >=0 <1.4.0 | 1.4.0 |
Published upstream
Mar 27, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 1, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 3, 2026
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.
Quoted source text, attributed separately from HOL analysis.