Live › vulnerability › CVE-2026-119186
node-forge is a JavaScript TLS and crypto library. Before 1.4.1, an AES-GCM decryption with a tagLength that converts to zero and an empty tag lets an attacker's modified ciphertext pass as authentic.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-29 20:26 UTC. All times on this page are UTC.
Applications that call node-forge's AES-GCM decryption with a tagLength value taken from received data, or one that is unset or zero, are exposed. Applications that omit tagLength to use the 128-bit default or pass a fixed valid tag length are not affected, according to the description.
No product ranges from the sources yet.
npm ls node-forge to find the installed version.forge.cipher.createDecipher and check whether tagLength is taken from received data or may be unset or zero.1.4.1Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
Forge (also called node-forge) is a native implementation of Transport Layer Security in JavaScript. Prior to 1.4.1, node-forge did not validate the AES-GCM tagLength option passed to start() during decryption through forge.cipher.createDecipher(). When an application derived tagLength from received data or used an unset or zero-like configuration value, a value that converted to zero together with an empty or missing authentication tag caused the calculated and supplied tags to compare as empty, so decipher.finish() accepted unauthenticated ciphertext. Applications that omit tagLength to use the 128-bit default or pass a fixed valid tag length are unaffected. This issue is fixed in version 1.4.1.
This page as .md · .json · in your agent: get_signal("CVE-2026-119186")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.