CVE-2026-33895

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.0%, top 87% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: NoneExposed: 0

A fix is available — apply it.

Forge (also called node-forge) is a native implementation of Transport Layer Security in JavaScript. Prior to version 1.4.0, Ed25519 signature verification accepts forged non-canonical signatures where the scalar S is not reduced modulo the group order (S >= L). A valid signature and its S + L variant both verify in forge, while Node.js crypto.verify (OpenSSL-backed) rejects the S + L variant, as defined by the specification. This class of signature malleability has been exploited in practice to bypass authentication and authorization logic (see CVE-2026-25793, CVE-2022-35961). Applications relying on signature uniqueness (i.e., dedup by signature bytes, replay tracking, signed-object canonicalization checks) may be bypassed. Version 1.4.0 patches the issue.

CVSS v3
7.5
EG Score
7.5(medium)
EPSS
26.9%
KEV
Not listed

Published

March 27, 2026

Last Modified

July 15, 2026

Advisory Details (3)

Auto-updated Jun 10, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github.
github Patch Available🟡 PoC Available

Signature forgery in Ed25519 due to missing S < L check · Advisory · digitalbazaar/forge · GitHub

https://github.com/digitalbazaar/forge/security/advisories/GHSA-q67f-28xg-22rw
github_commit

commit bdecf11571c9 (digitalbazaar/forge)

Fix landed in digitalbazaar/forge commit bdecf11571c9 — awaiting tagged release

https://github.com/digitalbazaar/forge/commit/bdecf11571c9f1a487cc0fe72fe78ff6dfa96b85
generic

RFC 8032 - Edwards-Curve Digital Signature Algorithm (EdDSA)

https://datatracker.ietf.org/doc/html/rfc8032#section-8.4

Frequently asked(5)

What is CVE-2026-33895?
CVE-2026-33895 is a high vulnerability published on March 27, 2026. Forge (also called node-forge) is a native implementation of Transport Layer Security in JavaScript. Prior to version 1.4.0, Ed25519 signature verification accepts forged non-canonical signatures where the scalar S is not reduced modulo the group order (S >= L). A valid signature and its S + L…
When was CVE-2026-33895 disclosed?
CVE-2026-33895 was first published in the National Vulnerability Database on March 27, 2026, with the most recent update on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-33895 actively exploited?
CVE-2026-33895 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 26.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-33895?
CVE-2026-33895 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-33895?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-33895, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-33895

Explore →

Is Your Infrastructure Affected by CVE-2026-33895?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.