CVE-2026-119192: 
Chainguard Analyse et atténuation de la vulnérabilité

Aperçu

CVE-2026-119192 is an RSA PKCS#1 v1.5 signature forgery vulnerability in the node-forge JavaScript cryptography library (npm package node-forge), tracked under GHSA-6qrw-m8cv-hcxf. The flaw allows unauthenticated attackers to forge RSA signatures without possessing the private key, specifically targeting RSA keys with a low public exponent (e=3). All versions of node-forge up to and including 1.4.0 are affected; the issue was fixed in version 1.4.1. The advisory was published on October 27, 2026, and added to the GitHub Advisory Database on November 10, 2026. It carries a CVSS v3.1 base score of 7.5 (High) (GitHub Advisory, Github Advisory).

Détails techniques

The root cause is classified as CWE-347 (Improper Verification of Cryptographic Signature). In lib/rsa.js, the key.verify() function with the default RSASSA-PKCS1-V1_5 scheme parses the recovered DigestInfo using the lenient BER parser asn1.fromDer() and validates it with asn1.validate() against digestInfoValidator — neither of which enforces canonical DER encoding. This allows acceptance of non-canonical encodings including: NULL parameters with content bytes (e.g., 05 40 <64 bytes>), non-NULL or constructed values in the parameters position, non-minimal (long-form) and indefinite lengths, and non-canonical OID encodings (padded subidentifiers, trailing bytes). These non-canonical forms leave attacker-controlled bytes inside an accepted DigestInfo structure. For RSA keys with a low public exponent (e=3), this slack space is sufficient to perform a BERserk/Bleichenbacher-style forgery — computing a cube root over integers to construct a value whose cube matches a block that node-forge accepts, without knowledge of the private key. The fix in 1.4.1 introduces _encodeDigestInfo(), which DER-encodes the expected DigestInfo and requires a byte-for-byte match per RFC 8017 section 8.2.2 (GitHub Advisory, Patch Commit).

Impact

Successful exploitation allows an unauthenticated remote attacker to forge RSA signatures that are accepted as valid by node-forge without possessing the corresponding private key. This directly undermines integrity guarantees for any application using publicKey.verify() with the default scheme, as well as X.509 certificate and PKCS#7 signature verification, which internally rely on the same code path. Practical exploitation is limited to RSA keys with a low public exponent (e=3); keys using the standard e=65537 are not practically affected. The impact is purely on integrity — there is no confidentiality or availability impact — but forged certificates or signatures could enable authentication bypass, code signing circumvention, or man-in-the-middle attacks in affected applications (GitHub Advisory).

Exploitabilité

A proof-of-concept (PoC) with concrete malformed DigestInfo byte sequences is publicly documented in the GitHub Security Advisory, providing sufficient detail to reproduce the vulnerability without additional research. The advisory includes specific byte sequences such as 30 33 30 0F 05 02 BE EF 04 20 <H> (NULL parameters with content) and 30 81 31 30 0D 05 00 04 20 <H> (non-minimal DigestInfo length) that cause publicKey.verify() to return true. A full standalone PoC script (tests/pocs/ghsa-2g46-22mc-6gwp.js) demonstrating keyless e=3 forgery was also included in the 1.4.1 release commit. Feedly classifies exploit confidence as medium, and there is no evidence of in-the-wild exploitation at this time. The CVE status is Reserved and no CISA KEV listing has been identified (Github Advisory, Patch Commit).

Étapes d’exploitation

  1. Identify target: Locate an application that uses node-forge ≤ 1.4.0 for RSASSA-PKCS1-v1_5 signature verification (publicKey.verify()) with an RSA public key where e=3.
  2. Obtain the target public key: Retrieve the RSA public key (modulus N, exponent e=3) from the target application, e.g., from an X.509 certificate or PKCS#7 structure.
  3. Choose a message to forge: Select the arbitrary message (e.g., 'hello world!') for which a valid-appearing signature is desired. Compute its SHA-256 digest.
  4. Construct a non-canonical DigestInfo block: Build an EMSA-PKCS1-v1_5 block (00 01 FF..FF 00 || DigestInfo) where the DigestInfo uses a non-canonical BER encoding — for example, include NULL parameters with extra content bytes (05 40 <64 bytes>) or use non-minimal length encodings. This creates attacker-controlled free bytes within the accepted structure.
  5. Compute the forged signature via cube root: Using the free bytes as slack, find an integer S such that S³ (mod N) produces a block matching the crafted EMSA-PKCS1-v1_5 structure. This is achieved by: (a) pinning the suffix (digest octets) by computing a modular cube root mod 2^(8×suffix_length), then (b) stepping candidates S = s0 + q×M until S³ falls within the window [prefix||00..00||suffix, prefix||FF..FF||suffix). The PoC script in tests/pocs/ghsa-2g46-22mc-6gwp.js implements this algorithm.
  6. Submit the forged signature: Pass the forged signature S and the message digest to the vulnerable publicKey.verify(digest, signature) — it returns true, accepting the forgery as valid.
  7. Leverage the forgery: Use the accepted forged signature to bypass authentication, impersonate a certificate authority, or pass PKCS#7 signature validation in the target application (GitHub Advisory, Patch Commit).

Indicateurs de compromis

  • Application Behavior: publicKey.verify() returning true for signatures that were not generated by the legitimate private key holder; unexpected acceptance of X.509 certificates or PKCS#7 signatures that fail validation in other libraries.
  • Logs: Application logs showing successful signature verification events for messages or certificates from unexpected or unknown sources; absence of the error 'ASN.1 object does not contain a valid RSASSA-PKCS1-v1_5 DigestInfo value.' (present only in patched 1.4.1) when processing malformed inputs.
  • Network: Receipt of RSA signatures with non-standard DigestInfo encodings — e.g., DigestInfo blocks with long-form length bytes (30 81 xx instead of 30 xx) or NULL parameters with non-zero content (05 02 BE EF) in TLS handshakes, signed JWTs, or PKCS#7 messages.
  • File System: Presence of node-forge versions ≤ 1.4.0 in node_modules/node-forge/package.json ("version": "1.x.x" where x < 4.1); presence of PoC scripts such as ghsa-2g46-22mc-6gwp.js in unexpected locations.

Atténuation et solutions de contournement

The primary remediation is to upgrade node-forge to version 1.4.1 or later, which enforces byte-for-byte canonical DER DigestInfo matching per RFC 8017 section 8.2.2 (forge v1.4.1 Release). As a workaround for environments that cannot immediately upgrade, avoid using RSA keys with a low public exponent (e=3) for signature verification; standard keys with e=65537 are not practically exploitable via this attack. Additionally, consider implementing supplementary verification controls (e.g., cross-validating signatures with a second cryptographic library) where signature integrity is critical (GitHub Advisory).

Réactions de la communauté

The vulnerability was independently reported by multiple researchers including Oren Yomtov (Fireblocks), Bronson Yen (Calif.io, in collaboration with Claude and Anthropic Research), Kamil Hałajda, and others, indicating broad community attention to RSA signature verification correctness in JavaScript libraries. The advisory notes AI-assisted discovery, reflecting a growing trend of AI-aided security research. The issue is part of a series of related node-forge signature forgery vulnerabilities (CVE-2026-33894, CVE-2026-85393), suggesting ongoing scrutiny of the library's ASN.1 parsing logic. Coverage appeared on OSV, VulnDB, and security radar platforms shortly after publication (Github Advisory).

Ressources supplémentaires

État de correction de la distribution Linux

Corrigez la disponibilité entre les grandes distributions Linux et leurs versions.

Ubuntu

Inconnu

focal (esm-apps)

node-node-forge

Inconnu

jammy

node-node-forge

Inconnu

jammy (esm-apps)

node-node-forge

Inconnu

Source: Ce rapport a été généré à l’aide de l’IA

Connexe Chainguard Vulnérabilités :

CVE ID

Gravité

Partition

Technologies

Nom du composant

Exploit CISA KEV

A corrigé

Date de publication

CVE-2026-114938HIGH8.1
  • Amazon Corretto JDK logoAmazon Corretto JDK
  • java-21-openjdk-static-libs-fastdebug
NonOuiNov 17, 2026
CVE-2026-119192HIGH7.5
  • Chainguard logoChainguard
  • argo-workflows-3.6
NonOuiNov 17, 2026
CVE-2026-129852MEDIUM6.9
  • Wolfi logoWolfi
  • seaweedfs
NonOuiNov 16, 2026
CVE-2026-119790MEDIUM6.3
  • Chainguard logoChainguard
  • zitadel-4
NonOuiNov 16, 2026
CVE-2026-121758MEDIUM5.9
  • Wolfi logoWolfi
  • glibc
NonNonNov 17, 2026

Évaluation gratuite des vulnérabilités

Évaluez votre posture de sécurité cloud

Évaluez vos pratiques de sécurité cloud dans 9 domaines de sécurité afin d’évaluer votre niveau de risque et d’identifier les lacunes dans vos défenses.

Évaluation de la demande

Ressources Wiz supplémentaires

Obtenez une démo personnalisée

Prêt(e) à voir Wiz en action ?

"La meilleure expérience utilisateur que j’ai jamais vue, offre une visibilité totale sur les workloads cloud."
David EstlickRSSI
"Wiz fournit une interface unique pour voir ce qui se passe dans nos environnements cloud."
Adam FletcherChef du service de sécurité
"Nous savons que si Wiz identifie quelque chose comme critique, c’est qu’il l’est réellement."
Greg PoniatowskiResponsable de la gestion des menaces et des vulnérabilités