CVE-2026-85393
node-forge allows RSA PKCS#1 v1.5 signature forgery via malformed DigestAlgorithm.
Is CVE-2026-85393 being exploited?
Not confirmed. CVE-2026-85393 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.20% probability of exploitation in the next 30 days.
How severe is CVE-2026-85393?
CVE-2026-85393 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-85393?
Yes. A fix has been recorded for CVE-2026-85393. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-85393 affect?
CVE-2026-85393 affects node-forge <= 1.4.0, applications using node-forge for RSA verification, npm packages bundling node-forge. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-85393?
Update node-forge to fixed release; audit and rotate low-exponent RSA keys.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Forge RSA PKCS#1 v1.5 signatures for arbitrary messages on low-exponent RSA keys, bypassing signature verification.
Immediate action required
- affected<= 1.4.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.