CVE-2026-33894: CWE-347: Improper Verification of Cryptographic Signature in digitalbazaar forge
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.
AI Analysis
Technical Summary
The vulnerability in digitalbazaar's forge library affects RSASSA PKCS#1 v1.5 signature verification for keys with a low public exponent (e=3). Prior to version 1.4.0, the verification process accepts signatures that include additional bytes within the ASN.1 structure, allowing attackers to craft forged signatures that pass validation. The lack of enforcement of the minimum 8-byte padding requirement as per the specification provides additional room for such forgery. This issue is similar to CVE-2022-24771 but differs in the placement of the extraneous bytes. The vulnerability enables Bleichenbacher-style signature forgery attacks. The issue is resolved in forge version 1.4.0.
Potential Impact
Successful exploitation allows attackers to forge cryptographic signatures, potentially enabling impersonation or bypass of signature-based authentication or integrity checks. The vulnerability does not impact confidentiality or availability but compromises signature integrity. No known exploits are reported in the wild at this time.
Mitigation Recommendations
Upgrade to digitalbazaar forge version 1.4.0 or later, where this vulnerability is patched. There are no alternative mitigations recommended as the fix is available in the official release.
CVE-2026-33894: CWE-347: Improper Verification of Cryptographic Signature in digitalbazaar forge
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.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in digitalbazaar's forge library affects RSASSA PKCS#1 v1.5 signature verification for keys with a low public exponent (e=3). Prior to version 1.4.0, the verification process accepts signatures that include additional bytes within the ASN.1 structure, allowing attackers to craft forged signatures that pass validation. The lack of enforcement of the minimum 8-byte padding requirement as per the specification provides additional room for such forgery. This issue is similar to CVE-2022-24771 but differs in the placement of the extraneous bytes. The vulnerability enables Bleichenbacher-style signature forgery attacks. The issue is resolved in forge version 1.4.0.
Potential Impact
Successful exploitation allows attackers to forge cryptographic signatures, potentially enabling impersonation or bypass of signature-based authentication or integrity checks. The vulnerability does not impact confidentiality or availability but compromises signature integrity. No known exploits are reported in the wild at this time.
Mitigation Recommendations
Upgrade to digitalbazaar forge version 1.4.0 or later, where this vulnerability is patched. There are no alternative mitigations recommended as the fix is available in the official release.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-03-24T15:41:47.489Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 69c6efce3c064ed76ff462e5
Added to database: 3/27/2026, 8:59:58 PM
Last enriched: 4/4/2026, 10:55:10 AM
Last updated: 5/11/2026, 9:37:22 PM
Views: 89
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.