CVE-2026-118774

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

Published Oct 29, 2026 CVSS 3.1 · 3.7 Low EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

The vulnerability occurs when the node-forge library incorrectly applies the RSA padding and RSASSA-PSS parameters from the issuer certificate instead of the child certificate being verified. As a result, a child certificate that declares the RSASSA-PSS signature algorithm may be accepted with a PKCS#1 v1.5 signature if the issuer uses PKCS#1 v1.5. This flaw does not allow a malicious actor to forge certificate identities because the signature must still be produced with the issuer’s private key. However it circumvents policies or audit checks that require the certificate chain to declare the same signature algorithm throughout the chain, potentially enabling a certificate formed to evade security checks.

Affected Systems

This issue affects the digitalbazaar:forge package (node-forge) and applies to any version prior to 1.4.1. Software that relies on node-forge for Transport Layer Security or certificate validation, such as custom TLS implementations in JavaScript environments, would be subject to the flaw until the library is upgraded.

Risk and Exploitability

The CVSS score of 3.7 classifies the risk as low, and the EPSS score of 0.00103 indicates a very low but nonzero exploitation probability. It is not listed in the CISA KEV catalog. The likely attack vector requires an attacker to supply a certificate chain to an application that uses node-forge for validation, and to control the issuer and child certificates to have mismatched signature algorithms. Because a valid private key must still be used, the vulnerability cannot be leveraged for privilege escalation or remote code execution, but it can break compliance and policy enforcement.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade the node-forge library to version 1.4.1 or newer.
  • If upgrading is not immediately possible, verify that the signature algorithm declared in a certificate matches the algorithm used to verify its signature before accepting the certificate. This can be added as an authorization check in the application logic.
  • Audit and tighten any TLS or certificate validation code paths to enforce consistent signature algorithm requirements across the chain and to document the check as part of security controls.

Generated by OpenCVE AI on November 6, 2026 at 02:07 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-9wg5-mj3p-v49q Forge: Certificate signature verified with the issuer's RSA signature scheme
History
Type Values Removed Values Added
CPEs cpe:2.3:a:digitalbazaar:forge:*:*:*:*:*:*:*:*
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Digitalbazaar
Digitalbazaar forge
Vendors & Products Digitalbazaar
Digitalbazaar forge
Type Values Removed Values Added
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.
Title Forge: Certificate signature verified with the issuer's RSA signature scheme
Weaknesses CWE-347
References
Metrics cvssV3_1

{'score': 3.7, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N'}

Weaknesses
  • CWE-295

    Improper Certificate Validation

  • CWE-347

    Improper Verification of Cryptographic Signature

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Nov 3, 2026, 4:17 PM
Reserved
Oct 28, 2026, 7:20 PM
Status
Analyzed
Published
Oct 29, 2026, 7:17 PM
Modified
Nov 4, 2026, 2:57 PM
Severity
Low
Public date
Oct 29, 2026, 6:33 PM