CVE-2026-118774: digitalbazaar forge · Improper Verification of Cryptographic Signature
Affects digitalbazaar forgeSource CVE Database V5
Not known to be exploited · CVSS 3.7 Low : upgrade to 1.4.1 when convenient.
Data as of 29 Oct 2026, 19:15 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 3.7 |
|---|
- Patch
- Available – fixed in 1.4.1
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 29 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Upgrade forge and digitalbazaar/forge to 1.4.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| digitalbazaarforge | Affected
| Fixed in
|
npmdigitalbazaar/forgepkg:npm/digitalbazaar/forgeOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade to forge version 1.4.1 or later, where this signature verification flaw is fixed. No other mitigation is required as the issue is resolved in the official patch.
Description
A cryptographic signature verification flaw exists in digitalbazaar's forge library versions prior to 1.4.1. The vulnerability involves improper verification of the signature scheme, where the library incorrectly uses the issuer certificate's RSA padding and RSASSA-PSS parameters instead of those from the child certificate. This could allow a child certificate labeled as RSASSA-PSS to be accepted with a PKCS#1 v1.5 signature if the issuer uses PKCS#1 v1.5. The flaw does not allow certificate identity forgery but may bypass policies enforcing specific signature schemes. The issue is resolved in version 1.4.1.