Vulnerability record · CVE-2026-85393 · published 3 September 2026

CVE-2026-85393: Improper verification of cryptographic signature vulnerability

node-forge through 1.4.0 fails to validate element count in nested DigestAlgorithm sequences during RSA PKCS#1 v1.5 signature verification. Attackers can embed garbage bytes inside the DigestAlgorithm sequence to forge valid signatures for arbitrary messages using low-exponent RSA keys. This is an incomplete fix for CVE-2026-33894.

8.7 CVSS 4.0 High EPSS 0.33% · top 76.8% CWE-347 · Improper verification of cryptographic signature Deferred

8.7CVSS 4.0 base score

0.33%EPSS exploitation probability, 30 days

NoNot in CISA KEV

0Affected product versions listed by NVD

7References

24 Sep 2026Last modified by NVD

Description

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:

References

Link	Tags
https://github.com/advisories/GHSA-ppp5-5v6c-4jwp
https://github.com/digitalbazaar/forge
https://github.com/digitalbazaar/forge/blob/v1.4.0/lib/asn1.js
https://github.com/digitalbazaar/forge/blob/v1.4.0/lib/rsa.js
https://github.com/digitalbazaar/forge/issues/1149
https://www.vulncheck.com/advisories/node-forge-through-1.4.0-rsa-pkcs-1-1.5-signature-forgery-via-nested-digestalgorith
https://github.com/advisories/GHSA-ppp5-5v6c-4jwp

Track CVE-2026-85393 inside VULONE

Watch it alongside the ransomware crews, C2 infrastructure and forum chatter that reference it, query it through the API and pull it into your SIEM over TAXII.

Start free Open in platform

Related vulnerabilities

Same products first, then exploited flaws of the same weakness class.

10.0CVE-2026-5430Wso2 api control plane improper verification of cryptographic signature vulnerabilityThe JWT authentication mechanism accepts tokens signed with algorithms other than those explicitly configured or supported. This allows an attacker t…KEVEPSS 0.59%6 Aug 2026 9.5CVE-2026-48558SimpleHelp OIDC authentication bypass via unverified token signatureSimpleHelp 5.5.15 and earlier and 6.0 pre-release versions accept OIDC identity tokens without verifying their cryptographic signature. When OIDC is …KEVEPSS 5.7%analysed12 Jun 2026 9.8CVE-2025-59718Fortinet FortiOS/FortiProxy SAML signature check bypass in FortiCloud SSOFortiOS, FortiProxy and FortiSwitchManager fail to properly verify the cryptographic signature of SAML responses used for FortiCloud SSO login. An un…KEVEPSS 68%analysed9 Dec 2025 4.6CVE-2025-47827IGEL OS Secure Boot bypass via improper signature verificationIGEL OS before version 11 fails to properly verify a cryptographic signature in the igel-flash-driver module, allowing Secure Boot to be bypassed. A …KEVEPSS 4.9%analysed5 Jun 2025 10.0CVE-2020-2021PAN-OS SAML signature verification bypass allows authentication bypassPAN-OS fails to properly verify SAML signatures when SAML authentication is enabled and the 'Validate Identity Provider Certificate' option is unchec…KEVEPSS 4.4%analysed29 Jun 2020 5.5CVE-2013-3900Windows WinVerifyTrust Authenticode signature verification RCECVE-2013-3900 is a remote code execution flaw in how the Windows WinVerifyTrust function verifies Authenticode signatures on portable executable file…KEVEPSS 45%analysed11 Dec 2013 7.8CVE-2020-1464Windows file signature validation spoofing allows loading of improperly signed filesWindows incorrectly validates file signatures, so a crafted file can be treated as properly signed. This lets an attacker bypass the security feature…KEVEPSS 39%analysed17 Aug 2020

Source: NIST National Vulnerability Database (record CVE-2026-85393), CISA KEV, FIRST EPSS (scores of 2026-09-27). This page is refreshed as NVD updates the record.