Forge has signature forgery in Ed25519 due to missing S > L check
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.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for help- Published
- Mar 27, 2026
- Updated
- Sep 4, 2026
- EPSS
- 0.5% · 38th percentile
- CWE
- CWE-347
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
30
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.5%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · GitHub_M
- 7.5
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| digitalbazaar | forge | cpe:2.3:a:digitalbazaar:forge |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- digitalbazaar forgeup to 1.3.3 inclusive
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
digitalbazaar forge
- < 1.4.0affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| npm | node-forge | before 1.4.0 | 1.4.0 |
| Red Hat:ansible_automation_platform_developer:2.5::el8 | python3.12-click | before 0:8.3.3-1.el8ap | 0:8.3.3-1.el8ap |
| Red Hat:ansible_automation_platform_developer:2.5::el8 | python3.12-cryptography | before 0:46.0.7-1.el8ap | 0:46.0.7-1.el8ap |
| Red Hat:ansible_automation_platform_developer:2.5::el8 | receptor | before 0:1.6.5-1.el8ap | 0:1.6.5-1.el8ap |
| Red Hat:ansible_automation_platform_developer:2.5::el9 | python3.12-click | before 0:8.3.3-1.el9ap | 0:8.3.3-1.el9ap |
| Red Hat:ansible_automation_platform_developer:2.5::el9 | python3.12-cryptography | before 0:46.0.7-1.el9ap | 0:46.0.7-1.el9ap |
| Red Hat:ansible_automation_platform_developer:2.5::el9 | receptor | before 0:1.6.5-1.el9ap | 0:1.6.5-1.el9ap |
| Red Hat:ansible_automation_platform:2.5::el8 | automation-controller-venv-tower | before 0:4.6.29-2.el8ap | 0:4.6.29-2.el8ap |
| Red Hat:ansible_automation_platform:2.5::el8 | automation-gateway-proxy-server | before 0:2.5.10-6.el8ap | 0:2.5.10-6.el8ap |
| Red Hat:ansible_automation_platform:2.5::el8 | automation-gateway-server | before 0:2.5.20260422-3.el8ap | 0:2.5.20260422-3.el8ap |
| Red Hat:ansible_automation_platform:2.5::el8 | python3.12-pillow | before 0:12.2.0-1.el8ap | 0:12.2.0-1.el8ap |
| Red Hat:ansible_automation_platform:2.5::el9 | automation-controller-venv-tower | before 0:4.6.29-2.el9ap | 0:4.6.29-2.el9ap |
| Red Hat:ansible_automation_platform:2.5::el9 | automation-gateway-proxy-server | before 0:2.6.14-3.el9ap | 0:2.6.14-3.el9ap |
| Red Hat:ansible_automation_platform:2.5::el9 | automation-gateway-server | before 0:2.5.20260422-3.el9ap | 0:2.5.20260422-3.el9ap |
| Red Hat:ansible_automation_platform:2.5::el9 | python3.12-pillow | before 0:12.2.0-1.el9ap | 0:12.2.0-1.el9ap |
Same product
digitalbazaar: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-33896Forge has a basicConstraints bypass in its certificate chain verification (RFC 5280 violation)36Monitor
- CVE-2026-85393node-forge through 1.4.0 RSA PKCS#1 v1.5 Signature Forgery via Nested DigestAlgorithm Padding34Monitor
- CVE-2025-66031node-forge ASN.1 Unbounded Recursion34Monitor
- CVE-2025-12816An interpretation-conflict (CWE-436) vulnerability in node-forge versions 1.3.1 and earlier enables unauthenticated attackers to craft ASN.134Monitor
- CVE-2026-33894Forge has signature forgery in RSA-PKCS due to ASN.1 extra field30Monitor
- CVE-2026-33891Forge has Denial of Service via Infinite Loop in BigInteger.modInverse() with Zero Input30Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| npm:node-forge | 1.4.0 | Package registry (OSV) |
| red hat:automation-controller-venv-tower | 0:4.6.29-2.el8ap · Red Hat:ansible_automation_platform:2.5::el8 | Package registry (OSV) |
| red hat:automation-gateway-proxy-server | 0:2.5.10-6.el8ap · Red Hat:ansible_automation_platform:2.5::el8 | Package registry (OSV) |
| red hat:automation-gateway-server | 0:2.5.20260422-3.el8ap · Red Hat:ansible_automation_platform:2.5::el8 | Package registry (OSV) |
| red hat:python3.12-click | 0:8.3.3-1.el8ap · Red Hat:ansible_automation_platform_developer:2.5::el8 | Package registry (OSV) |
| red hat:python3.12-cryptography | 0:46.0.7-1.el8ap · Red Hat:ansible_automation_platform_developer:2.5::el8 | Package registry (OSV) |
| red hat:python3.12-pillow | 0:12.2.0-1.el8ap · Red Hat:ansible_automation_platform:2.5::el8 | Package registry (OSV) |
| red hat:receptor | 0:1.6.5-1.el8ap · Red Hat:ansible_automation_platform_developer:2.5::el8 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-85393160 days apartnode-forge through 1.4.0 RSA PKCS#1 v1.5 Signature Forgery via Nested DigestAlgorithm Padding34Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- high · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
CWE-347 · Improper Verification of Cryptographic SignatureCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
nvd-secondary
Root cause
The verifier takes the algorithm to verify with from the token’s own header. Untrusted data ends up deciding its own verification rule.
The bug in code
The whole CWE-347 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
const claims = jwt.verify(token, publicKey);Fixed
const claims = jwt.verify(token, publicKey, { algorithms: ["RS256"], issuer: "https://id.example.com", audience: "portal",});Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- datatracker.ietf.org/doc/html/rfc8032#section-8.4
- github.com/digitalbazaar/forge/commit/bdecf11571c9f1a487cc0fe72fe78ff6dfa96b85
- github.com/digitalbazaar/forge/security/advisories/GHSA-q67f-28xg-22rw
- access.redhat.com/errata/RHSA-2026:13826
- access.redhat.com/errata/RHSA-2026:24761
- access.redhat.com/errata/RHSA-2026:34342
- access.redhat.com/errata/RHSA-2026:9742
- access.redhat.com/security/cve/CVE-2026-33895
- bugzilla.redhat.com/show_bug.cgi?id=2452457
- security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-33895.json
Vendor advisories and official records. Exploit/PoC links are deliberately left out.