CVE-2026-118776: Forge: Incomplete PKCS#7 padding validation in AES/DES CBC and ECB decryption

CVE-2026-118776 · Severity: low · CVSS 3.7 · Published 2026-10-29

Forge (also called node-forge) is a native implementation of Transport Layer Security in JavaScript. Prior to 1.4.1, the affected implementation used decipher.finish(), CBC and ECB modes, PKCS#7 padding to process the relevant input or security decision. node-forge validated only the final byte of PKCS#7 padding during CBC and ECB decryption and accepted zero, oversized, or mismatched padding bytes. Malformed ciphertext could consequently be accepted and up to four plaintext blocks could be silently removed, causing an integrity failure in applications that treated successful decryption as proof of valid padding. This issue is fixed in version 1.4.1.

Technologies: node-forge (npm). Vendors: npm.

Quick answers

Is CVE-2026-118776 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-118776 being exploited in the wild.
How severe is CVE-2026-118776?
Low severity, with a CVSS score of 3.7, published 29 October 2026.
Which products and versions are affected?
node-forge (npm) <= 1.4.0, SEMVER:introduced=0,fixed=1.4.1.
Is there a fix for CVE-2026-118776?
Yes. node-forge (npm): upgrade to 1.4.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2026-118776?
Check whether you run node-forge (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • node-forge (npm): upgrade to 1.4.1 or later
    npm install node-forge@1.4.1

Affected products

  • node-forge (npm) <= 1.4.0, SEMVER:introduced=0,fixed=1.4.1

Identifiers

  • CVE-2026-118776
  • GHSA-2vgq-wchc-25w7

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.