Skip to main content
VulnerabilityPublished Updated

CVE-2026-118779: Node node forge · Prior to 1.4.1, the affected implementation used pem.decode(), lib/pem.js, missing

Affects node-node-forgeSource GCVE Database

0
Compare
Authoritative record:CVE-2026-118779· High 7.5

Not known to be exploited · CVSS 7.5 High · fixed in 1.4.1 : patch node-node-forge soon.

Data as of 5 Nov 2026, 12:35 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.17.5
Patch
Available – fixed in 1.4.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 29 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
Ubuntu 22.04 LTSnode-node-forgepkg:deb/ubuntu/node-node-forge?arch=source&distro=jammyOther threatsAffected
  • =0.10.0~dfsg-3
  • =1.2.1~dfsg-2
Fixed in–
Ubuntu 20.04 LTSnode-node-forgepkg:deb/ubuntu/node-node-forge?arch=source&distro=focalOther threatsAffected
  • =0.8.5~dfsg-2
  • =0.9.1~dfsg-1
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

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.

References

Community reviews

Loading reviews…