Skip to content
OpenAdvisories
Low · 3.7 CVE-2026-118774 EUVD-2026-113331GHSA-9wg5-mj3p-v49q

Forge: Certificate signature verified with the issuer's RSA signature scheme

Published Oct 29, 2026 · Updated Nov 3, 2026 · Assigned by GitHub_M

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.

Affected products

VendorProductAffectedFixed
digitalbazaar forge < 1.4.1 —

Fixed in Linux distributions

Distributions backport fixes, so the version that fixes this vulnerability differs per release — upgrade to at least the version shown. From the distributions' security trackers and advisories.

ReleasePackageFixed inAdvisory
Ubuntu 22.04 LTS node-node-forge No fix yet —
Ubuntu 20.04 LTS node-node-forge No fix yet —

Azure Linux

ReleasePackageFixed inAdvisory
Azure Linux 3 python-tensorboard No fix yet —

Affected packages

EcosystemPackageAffectedFixedRecord
npm node-forge < 1.4.1 1.4.1 GHSA-9wg5-mj3p-v49q

References