Digital Bazaar node-forge: ReDoS in pem.decode() (CVE-2026-118779)
Digital Bazaar node-forge versions prior to 1.4.1 are vulnerable to a Regular Expression Denial of Service (ReDoS) in the pem.decode() function, allowing unauthenticated attackers to cause high CPU usage via malformed PEM input.
CVE search metadata
CVE search record: CVE-2026-118779. Severity: high. CVSS: 7.5. KEV: no. Product: node-forge (< 1.4.1). Brief: Digital Bazaar node-forge: ReDoS in pem.decode() (CVE-2026-118779). Brief link: https://feed.craftedsignal.io/briefs/2026-10-node-forge-redos/
CVE search record: CVE-2026-118782. Severity: high. CVSS: 7.5. KEV: no. Product: node-forge (< 1.4.1). Brief: Digital Bazaar node-forge: ReDoS in pem.decode() (CVE-2026-118779). Brief link: https://feed.craftedsignal.io/briefs/2026-10-node-forge-redos/
Triage facts
Revision 1- Applicability
- node-forge (< 1.4.1)
- Evidence
- Unknown
- Severity
- High
- Action
- Elevated
- Sources
- 2 public sources
- Freshness
- Revision 1Oct 29, 20:40 UTC
- Vulnerabilities
- 2 CVEs
- Source quality
- A1Likely
What's new
- 1. added coverage for node-forge (< 1.4.1) Oct 29, 20:40 via nvd
The node-forge library, a native JavaScript implementation of TLS, contains a vulnerability in its pem.decode() function within lib/pem.js. The library uses polynomial-time regular expressions to process PEM input, including the search for matching END lines and the parsing of encapsulated headers. An unauthenticated attacker can supply crafted, malformed PEM input to any high-level parser relying on this function, triggering catastrophic backtracking that leads to excessive CPU consumption and denial of service. This vulnerability is identified as CVE-2026-118779.
Impact
Successful exploitation results in high CPU utilization, potentially leading to a denial-of-service condition for applications relying on the node-forge library to process user-supplied PEM files or certificates.
Recommendation
- Upgrade the node-forge library to version 1.4.1 or later immediately.
- Inventory applications within the environment that utilize the node-forge library for certificate or PEM parsing.
- Review input validation controls for services that ingest PEM-encoded data to ensure length and complexity constraints are enforced before processing by the library.
Immediate actions
Patch node-forge to 1.4.1 or later in all identified applications
Threat Hunt
Identify applications utilizing node-forge versions < 1.4.1 that accept PEM input from untrusted sources
Data: Application dependency manifests (package.json, yarn.lock, etc.)
Identify applications using node-forge versions below 1.4.1
Data: Software Bill of Materials (SBOM) or package-lock.json / yarn.lock files
Mitigations
Upgrade node-forge to version 1.4.1
CVE-2026-118779
Upgrade node-forge to 1.4.1 or later
CVE-2026-118782