Skip to main content
VulnerabilityPublished Updated

CVE-2026-119186: Node node forge · Prior to 1.4.1, node-forge did not validate the AES-GCM tagLength option passed to

Affects node-node-forgeSource GCVE Database

0
Compare
Authoritative record:CVE-2026-119186· Medium 5.9

Not known to be exploited · CVSS 5.9 Medium · fixed in 1.4.1 : update node-node-forge when convenient.

Data as of 5 Nov 2026, 12:35 UTC

CVSS 3.1 base score
5.9Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.15.9
Patch
Available – fixed in 1.4.1
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 29 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
Ubuntu 22.04 LTSnode-node-forgepkg:deb/ubuntu/node-node-forge?arch=source&distro=jammyOther threatsAffected
  • =0.10.0~dfsg-3
  • =1.2.1~dfsg-2
Fixed in–
Ubuntu 20.04 LTSnode-node-forgepkg:deb/ubuntu/node-node-forge?arch=source&distro=focalOther threatsAffected
  • =0.8.5~dfsg-2
  • =0.9.1~dfsg-1
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

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.

References

Community reviews

Loading reviews…