Skip to content
OpenAdvisories
Medium · 5.9 CVE-2026-119186 EUVD-2026-113363GHSA-5cwg-6vw7-rj6p

Forge: AES-GCM authentication bypass via unvalidated tagLength option

Published Oct 29, 2026 · Updated Oct 29, 2026 · Assigned by GitHub_M

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.

Affected products

VendorProductAffectedFixed
digitalbazaar forge < 1.4.1 —

Fixed in Linux distributions

Distributions backport fixes, so the version that fixes this vulnerability differs per release — upgrade to at least the version shown. From the distributions' security trackers and advisories.

ReleasePackageFixed inAdvisory
Ubuntu 22.04 LTS node-node-forge No fix yet —
Ubuntu 20.04 LTS node-node-forge No fix yet —

Azure Linux

ReleasePackageFixed inAdvisory
Azure Linux 3 python-tensorboard No fix yet —

Wolfi

ReleasePackageFixed inAdvisory
Wolfi rolling jitsucom-jitsu-console 2.11.0-r42 —
Wolfi rolling kubeflow-centraldashboard 2.0.0-r8 —

Affected packages

EcosystemPackageAffectedFixedRecord
npm node-forge < 1.4.1 1.4.1 GHSA-5cwg-6vw7-rj6p

References