Low severity · published Oct 29, 2026
CVE-2026-118774
Forge: Certificate signature verified with the issuer's RSA signature scheme
New
3.7
CVSS
–
EPSS
No
On KEV
Description
Forge (also called node-forge) is a native implementation of Transport Layer Security in JavaScript. Prior to 1.4.1, the affected implementation used certificate.verify(child), _verifySignature(), lib/x509.js to process the relevant input or security decision. node-forge selected RSA padding and RSASSA-PSS parameters from the issuer certificate rather than the child certificate being verified. A child labeled as RSASSA-PSS could therefore be accepted with a PKCS#1 v1.5 signature when the issuer used PKCS#1 v1.5. The signature still had to be produced with the trusted issuer's private key, so this did not permit certificate identity forgery, but it could bypass policies that require a declared signature scheme. This issue is fixed in version 1.4.1.
CVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
Attack vector
Network
Complexity
High
Privileges
None
User interaction
None
Confidentiality
None
Integrity
Low
Availability
None
Scope
Unchanged
Exploitation
Is it being used?
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
FO
forge · digitalbazaar
< 1.4.1 · source: vendor
Affected product
FO
forge
digitalbazaar
More from forge
9.1
CVE-2026-33896
Forge has a basicConstraints bypass in its certificate chain verification (RFC 5280 violation)
8.6
CVE-2025-12816
No description published yet
7.5
CVE-2026-119191
Forge: ASN.1 resource exhaustion via BIT STRING decoding in asn1.fromDer
7.5
CVE-2026-119188
Forge: Denial of service in TLS record processing via a record interleaved with a fragmented handshake message
7.5
CVE-2026-119187
Forge: Denial of service in TLS record processing via call stack exhaustion