cve.bz

CVE-2026-118779 digitalbazaar forge: Uncontrolled Resource Consumption

7.5 highExploit referenceEPSS 0.7%Fix available

High (7.5) in digitalbazaar forge. EPSS 0.7% estimated probability of exploitation activity in the next 30 days. Fixed in node-forge 1.4.1.

On this page
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.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
0.7% (unchanged from 0.7% a week ago) estimated probability of exploitation activity in the next 30 days; 53rd percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: yes · Technical impact: partial, assessed 2026-10-29. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-400 Uncontrolled Resource Consumption
CWE-1333 Inefficient Regular Expression Complexity
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-118779 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-118779?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-118779?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-118779 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
digitalbazaar:forgebefore 1.4.1

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-7wch-p9px-956xnpmnode-forge<1.4.11.4.1

Linux distributions

DistributionReleasePackageFixed inAdvisory
Ubuntu20.04:LTS, 22.04:LTSnode-node-forgeno fix listedUBUNTU-CVE-2026-118779
Azure Linux3python-tensorboardno fix listedAZL-112469

From the distributions' data via OSV.dev: Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Microsoft's Azure Linux vulnerability data, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Ubuntu.

Red Hat

Red Hat rates this Important.

Red Hat's statement

Red Hat Product Security rates this vulnerability as Important because an unauthenticated remote attacker can trigger significant CPU consumption and stall service event loops without requiring privileges or user interaction. In affected environments where applications ingest untrusted certificate or key payloads, processing maliciously constructed data can exhaust server resources and disrupt availability for legitimate users. Confidentiality and data integrity remain unaffected, as the weakness cannot be leveraged for remote execution or information exposure.

ProductPackageStateAdvisory
Node HealthCheck Operatorworkload-availability/node-healthcheck-must-gather-rhel9Affected
Node HealthCheck Operatorworkload-availability/node-healthcheck-operator-bundleAffected
Node HealthCheck Operatorworkload-availability/node-healthcheck-rhel9-operatorAffected
Node HealthCheck Operatorworkload-availability/node-remediation-console-rhel8Affected
OpenShift Pipelinesopenshift-pipelines/pipelines-hub-ui-rhel8Not affected
OpenShift Pipelinesopenshift-pipelines/pipelines-hub-ui-rhel9Affected
OpenShift Serverlessopenshift-serverless-1/logic-rhel9-operatorNot affected
OpenShift Service Mesh 3openshift-service-mesh/kiali-operator-bundleNot affected
OpenShift Service Mesh 3openshift-service-mesh/kiali-rhel9-operatorNot affected
Red Hat AMQ Broker 7amq-broker-bin.zipNot affected
Red Hat AMQ Broker 7amq-broker-maven-repository.zipAffected
Red Hat Ansible Automation Platform 2ansible-automation-platform-24/lightspeed-rhel8Fix deferred
Red Hat Ansible Automation Platform 2automation-controllerFix deferred
Red Hat Ansible Automation Platform 2automation-eda-controllerFix deferred
Red Hat Ansible Automation Platform 2automation-gatewayFix deferred
Red Hat Ansible Automation Platform 2automation-platform-uiAffected
Red Hat build of Apache Camel for Spring Boot 4rhaf-camel-for-springboot-maven-repository.zipNot affected
Red Hat build of Apache Camel for Spring Boot 4rhaf-camel-spring-boot-maven-repository.zipNot affected
Red Hat Build of Podman Desktoprh-podman-desktopAffected
Red Hat Ceph Storage 4rhceph/rhceph-4-dashboard-rhel8Fix deferred
24 more in the JSON and on Red Hat's page.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-118779.

Attack patterns (CAPEC)

  • CAPEC-492 Regular Expression Exponential Blowup
  • CAPEC-147 XML Ping of the Death Likelihood: Low · Severity: Medium
  • CAPEC-227 Sustained Client Engagement

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

History

  1. Analyzed by the NVD

Changes since this site first stored the record. The same for every record: /api/public/changes.

References

Check your stackJSON