CVE-2026-119186
Forge (also called node-forge) is a native implementation of …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/digitalbazaar/forge/commit/236845d96c71207259f91638d0138bba8e2fd624
- github.com/digitalbazaar/forge/releases/tag/v1.4.1
- github.com/digitalbazaar/forge/security/advisories/GHSA-5cwg-6vw7-rj6p
- nvd.nist.gov/vuln/detail/CVE-2026-119186
- github.com/advisories/GHSA-5cwg-6vw7-rj6p
- nvd.nist.gov/vuln/detail/CVE-2026-119186
- cve.org/CVERecord?id=CVE-2026-119186
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.