p PatchFirst

CVE-2026-119186

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

This page contains facts from public vulnerability sources. Check the original advisory before updating.

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.

CVSS 5.9 · Medium · EPSS 0.2% · Public exploit · Fix available

Published
Updated

Stack: system · node

Affected products and versions

  • forge

    Versions
    • < 1.4.1: Affected

    No fix published

  • node-forge npm

    Affected ranges
    • SEMVER: < 1.4.1

    Update to 1.4.1

  • node-node-forge Ubuntu:20.04:LTS

    Versions
    • 0.8.5~dfsg-2
    • 0.9.1~dfsg-1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • node-node-forge Ubuntu:22.04:LTS

    Versions
    • 0.10.0~dfsg-3
    • 1.2.1~dfsg-2
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

Original sources

Check your server →