ETK-2026-2729Zero's internal tracking ID, independent of the CVE number.

waiting for further signalsZero needs more public information before it can validate it.

GHSA-7wch-p9px-956x ↗

no check availablenot proven exploitable
awaiting cvepublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
npm:node-forge <= 1.4.0
fixed in 1.4.1
CWE-400 Uncontrolled Resource Consumption
ETK-2026-2729Zero's internal tracking ID, independent of the CVE number., no cve assigned
pkg:npm/node-forge
2h 52msince last run
16mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org, not yet published
trigger signal −3hwaiting for further signals−2h52m
−2h
−1h
0

description

node-forge versions before 1.4.1 can consume excessive processing time while decoding malformed PEM content. An unauthenticated attacker able to submit PEM text to an application can delay the Node.js event loop and disrupt service.

mitigation

Upgrade node-forge to version 1.4.1 or later. Until upgrades are complete, reject untrusted PEM inputs above a small size limit before passing them to node-forge; this reduces, but does not eliminate, exposure.

fixed in 1.4.1

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
16m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
not published yet
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-27 05:09Z

this entry in the feed

GET /api/v1/feed/ETK-2026-2729

{
  "etk_id": "ETK-2026-2729",
  "cve_id": null,
  "display_id": "ETK-2026-2729",
  "ghsa_id": "GHSA-7wch-p9px-956x",
  "euvd_id": null,
  "status": "published",
  "anchor_state": "awaiting_cve",
  "title": "Regular expression denial of service in node-forge PEM parsing",
  "summary": "node-forge versions before 1.4.1 can consume excessive processing time while decoding malformed PEM content. An unauthenticated attacker able to submit PEM text to an application can delay the Node.js event loop and disrupt service.",
  "mitigation": "Upgrade node-forge to version 1.4.1 or later. Until upgrades are complete, reject untrusted PEM inputs above a small size limit before passing them to node-forge; this reduces, but does not eliminate, exposure.",
  "vendor": "npm",
  "product": "npm:node-forge",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "<= 1.4.0"
      ],
      "ecosystem": "npm",
      "fixed_versions": [
        "1.4.1"
      ],
      "package_name": "node-forge",
      "purl": "pkg:npm/node-forge"
    }
  ],
  "cwes": [
    400
  ],
  "cvss_score": 7.5,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 15.996750433333334,
  "t0_at": null,
  "signals": {
    "trigger_signal": {
      "at": "2026-10-27T05:09:21+00:00",
      "days": -0.12518501167824075,
      "is_lower_bound": true,
      "measured_at": "2026-10-27T08:09:37.012455+00:00",
      "url": "https://github.com/digitalbazaar/forge/security/advisories/GHSA-7wch-p9px-956x"
    }
  }
}

published 2026-10-27 05:44Z
last change 2026-10-27 07:45Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.