Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-33894: CWE-347: Improper Verification of Cryptographic Signature in digitalbazaar forge

0
High
VulnerabilityCVE-2026-33894cvecve-2026-33894cwe-347cwe-20
Published: Fri Mar 27 2026 (03/27/2026, 20:45:49 UTC)
Source: CVE Database V5
Vendor/Project: digitalbazaar
Product: 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

AILast updated: 03/27/2026, 21:15:33 UTC

Technical Analysis

The vulnerability CVE-2026-33894 affects the digitalbazaar forge library, a JavaScript native implementation of TLS, specifically its RSASSA PKCS#1 v1.5 signature verification mechanism. Prior to version 1.4.0, forge improperly validates cryptographic signatures when the public exponent is low (e=3), a scenario that is susceptible to Bleichenbacher-style signature forgery attacks. The core issue lies in the acceptance of forged signatures that contain extraneous or “garbage” bytes embedded within the ASN.1 structure of the signature rather than outside it, which deviates from the expected strict ASN.1 encoding rules. This subtle difference allows attackers to craft signatures that pass verification despite being invalid. Furthermore, forge does not enforce the PKCS#1 specification requirement that signatures include at least 8 bytes of padding, providing additional room for attackers to manipulate the signature structure to bypass verification. This vulnerability is similar in nature to CVE-2022-24771 but differs in the method of embedding the extraneous bytes. The vulnerability impacts the integrity of cryptographic operations relying on forge’s signature verification, potentially allowing attackers to impersonate legitimate signers or bypass authentication mechanisms that depend on these signatures. The vulnerability has a CVSS 3.1 base score of 7.5 (high severity), with an attack vector of network, low attack complexity, no privileges required, and no user interaction needed. The scope is unchanged, and the impact affects integrity but not confidentiality or availability. No known exploits are reported in the wild as of the publication date. The issue was resolved in forge version 1.4.0 by enforcing stricter ASN.1 parsing and padding validation.

Potential Impact

The primary impact of this vulnerability is the compromise of data integrity in systems relying on forge for cryptographic signature verification. Attackers can forge signatures on arbitrary data, potentially allowing unauthorized code execution, bypass of authentication or authorization controls, and impersonation of trusted entities. This can lead to severe consequences in applications such as secure communications, software update validation, digital document signing, and any system relying on RSASSA PKCS#1 v1.5 signatures. Since the vulnerability requires no privileges or user interaction and can be exploited remotely, it poses a significant risk to exposed services and client applications using vulnerable forge versions. Organizations using forge in web applications, APIs, or embedded devices may face increased risk of targeted attacks or supply chain compromises. The lack of confidentiality or availability impact limits the scope to integrity, but integrity breaches in cryptographic contexts are often critical. The absence of known exploits suggests a window of opportunity for attackers if patches are not applied promptly.

Mitigation Recommendations

1. Immediately upgrade all instances of digitalbazaar forge to version 1.4.0 or later, which includes the patch for this vulnerability. 2. Audit all applications and services that use forge for cryptographic signature verification to identify vulnerable versions. 3. Implement additional cryptographic validation layers where feasible, such as verifying signatures with alternative libraries or hardware security modules (HSMs) to reduce reliance on a single implementation. 4. Enforce strict input validation and ASN.1 parsing rules in custom cryptographic code to prevent similar forgery attacks. 5. Monitor network traffic and logs for anomalous signature verification failures or suspicious signature patterns indicative of exploitation attempts. 6. Educate developers and security teams about the risks of using low public exponent keys (e=3) and encourage migration to more secure key parameters (e.g., e=65537). 7. For critical systems, consider implementing cryptographic agility to allow rapid switching to patched or alternative libraries in response to vulnerabilities. 8. Regularly review and update cryptographic dependencies to incorporate security patches promptly.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

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: 3/27/2026, 9:15:33 PM

Last updated: 3/28/2026, 1:30:43 AM

Views: 6

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

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

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses