Description
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 products
digitalbazaar: forge
References10
- github.com/digitalbazaar/forge/security/advisories/GHSA-ppp5-5v… Vendor Advisory
- datatracker.ietf.org/doc/html/rfc2313#section-8 Third Party Advisory
- mailarchive.ietf.org/arch/msg/openpgp/5rnE9ZRN1AokBVj3VqblGlP63… Third Party Advisory
- www.rfc-editor.org/rfc/rfc8017.html Third Party Advisory
- access.redhat.com/errata/RHSA-2026:13826
- access.redhat.com/errata/RHSA-2026:19375
- access.redhat.com/errata/RHSA-2026:21017
- access.redhat.com/errata/RHSA-2026:22465
- access.redhat.com/errata/RHSA-2026:22629
- access.redhat.com/errata/RHSA-2026:22840
Metrics
- CVSS 3.1
-
7.5
HIGH
Score source: CNA
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N - EPSS — exploit probability
- 0% percentile: 42 · as of 12 November 2026
- CWE
- CWE-20CWE-347
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.