Breaking News: Thousands Of GitHub Accounts Hijacked With wfx-loot CI Secret
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2026-118776

node-forge: node-forge: Data integrity failure via improper PKCS#7 padding validation

Overview

Published
29 Oct 2026
Modified
4 Nov 2026
Medium CVE
3 Registry packages
24 OS packages
4 Linux distributions
Yes Fix available

Description

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.

Source: OX vulnerability database

Severity

5.3 · MEDIUM

CVSS 3.1 base score, scored by NVD.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Weakness: CWE-20, CWE-354

Affected packages · 3

Packages affected by CVE-2026-118776
EcosystemPackageVulnerableFixed in
npm node-forge <1.4.1 1.4.1
Seal npm @seal-security/node-forge >=0.10.0-sp1-for-passport-saml, <0.10.0-sp999>=1.3.0-sp1, <1.3.0-sp999>=1.3.1-sp1, <1.3.1-sp999>=1.3.2-sp1, <1.3.2-sp999>=1.3.3-sp1, <1.3.3-sp999+1 more 0.10.0-sp9991.3.0-sp9991.3.1-sp9991.3.2-sp9991.3.3-sp999
Seal npm node-forge >=0.10.0-sp0, <0.10.0-sp999>=1.3.0-sp0, <1.3.0-sp999>=1.3.1-sp0, <1.3.1-sp999>=1.3.2-sp0, <1.3.2-sp999>=1.3.3-sp0, <1.3.3-sp999+1 more 0.10.0-sp9991.3.0-sp9991.3.1-sp9991.3.2-sp9991.3.3-sp999

Open a package to see all its vulnerabilities.

Operating systems · 9 fixes

Red Hat 3 releases · 2 packages

eol 2 affected 2
rhceph-rhceph-4-dashboard-rhel8 grafana
Red Hat fixes for CVE-2026-118776
ReleasePackageFixed in
7 rhceph-rhceph-4-dashboard-rhel8 eol
8 grafana +15 affected
8 rhceph-rhceph-4-dashboard-rhel8 eol
9 grafana +3 affected

chainguard 1 release · 2 packages

fixed 2
gitlab-rails-ce-18-10 gitlab-rails-ce-18-9
chainguard fixes for CVE-2026-118776
ReleasePackageFixed in
gitlab-rails-ce-18-10 18.10.8-r12
gitlab-rails-ce-18-9 18.9.8-r15

debian 1 release · 1 package

affected 1
node-node-forge
debian fixes for CVE-2026-118776
ReleasePackageFixed in
11 node-node-forge affected

minimos 1 release · 2 packages

fixed 2
argo-workflows-3-6 argo-workflows-3-7
minimos fixes for CVE-2026-118776
ReleasePackageFixed in
argo-workflows-3-6 +1 3.6.17-r0
argo-workflows-3-7 +1 3.7.8-r0

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.