
PEACH
Un cadre d’isolation des locataires
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).
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).
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).
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).
publicKey.verify()) with an RSA public key where e=3.'hello world!') for which a valid-appearing signature is desired. Compute its SHA-256 digest.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.tests/pocs/ghsa-2g46-22mc-6gwp.js implements this algorithm.publicKey.verify(digest, signature) — it returns true, accepting the forgery as valid.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.'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.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.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.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).
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).
Corrigez la disponibilité entre les grandes distributions Linux et leurs versions.
Source: Ce rapport a été généré à l’aide de l’IA
Évaluation gratuite des vulnérabilités
É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.
Obtenez une démo personnalisée
"La meilleure expérience utilisateur que j’ai jamais vue, offre une visibilité totale sur les workloads cloud."
"Wiz fournit une interface unique pour voir ce qui se passe dans nos environnements cloud."
"Nous savons que si Wiz identifie quelque chose comme critique, c’est qu’il l’est réellement."