Forge: AES-GCM authentication bypass via unvalidated tagLength option (digitalbazaar forge)

CVE-2026-119186
MEDIUM 5.9

At a glance

Source
NVD
State
PUBLISHED
Published
Updated
Assigner
GitHub_M
NVD status
Undergoing Analysis

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.

Weaknesses (CWE)

  • CWE-354 — Improper Validation of Integrity Check Value
  • CWE-1284 — Improper Validation of Specified Quantity in Input

References

Scores

VersionScoreVectorScored by
CVSS 3.1MEDIUM 5.9CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:NGitHub_M
CVSS 3.1MEDIUM 5.9CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:NNVD · security-advisories@github.com (Secondary)

European references

Affected products

ProductVersions
digitalbazaar · forgeaffected < 1.4.1

Sources

SourceLicence
CVE List (CVEProject cvelistV5)CVE Program Terms of Use
ENISA EUVDENISA — reproduction authorised, source acknowledged
NVD (NIST) via fkie-cad/nvd-json-data-feedsPublic domain — this product uses data from the NVD API but is not endorsed or certified by the NVD