CVE-2026-118779
🟡 Lownode-forge (npm) · < 1.4.1
CVSS (Koffei note)
7.5CVSS (v3.1, CVE List)
7.5EPSS (2026-11-18)
0.669%52.69th percentile
Exploitation
Not confirmed — CISA SSVC: exploitation poc, automatable yes, technical impact partial (a PoC is recorded); no in-the-wild exploitation read ; not in KEV (cisagov mirror, 18/11/2026) ; the Tenable TNS-2026-35 bulletin mentions no exploitation (Daily note of 17/11/2026)
Timeline
- 29/10/2026CVE record published (CVE List)
- 17/11/2026Tenable Identity Exposure 3.93.7 and 3.77.19 fix 52 flaws in bundled components
Risk
7.5 High (v3.1, GitHub CNA) — AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, EPSS 0.556% (CWE-400: Forge: Regular expression denial of service in PEM decoding (pem.decode))
Fix
Yes — node-forge 1.4.1 (record), 1.4.3 bundled in Tenable Identity Exposure 3.93.7 / 3.77.19 (TNS-2026-35)
Official 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 pem.decode(), lib/pem.js, missing END line to process the relevant input or security decision. node-forge used polynomial-time regular expressions in pem.decode(), including when searching for a matching END line and parsing encapsulated headers. An unauthenticated attacker able to supply PEM input to any high-level parser could consume excessive CPU with a long malformed message and cause denial of service. This issue is fixed in version 1.4.1.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CWE-1333,CWE-400