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

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

GHSA-834v-8h66-3h79 ↗

no check availablenot proven exploitable
awaiting cvepublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).−8h56mkevAttacks confirmed in the real world.
npm:happy-dom >= 17.0.0, <= 21.0.3
fixed in =>21.0.4
CWE-94 Improper Control of Generation of Code ('Code Injection')
ETK-2026-2206Zero's internal tracking ID, independent of the CVE number., no cve assigned
pkg:npm/happy-dom
9h 09msince last run
9mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
waiting for further signals−0h13mtrigger signal +0hpublic poc+0h
+2h
+4h
+6h
+8h
+10h

description

happy-dom before 21.0.4 may generate executable JavaScript from malformed ESM import aliases. Attackers who can provide HTML or module content can potentially run code as the Node.js process when JavaScript evaluation is enabled.

mitigation

Upgrade happy-dom to =>21.0.4 or later.

fixed in =>21.0.4

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
9m
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).
−8h56m
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual: an exploit technique exists, but no deterministic check could cover this one.

source signals

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

  1. 2026-10-20 18:13Z
  2. 2026-10-20 18:13Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-2206",
  "cve_id": null,
  "display_id": "ETK-2026-2206",
  "ghsa_id": "GHSA-834v-8h66-3h79",
  "euvd_id": null,
  "status": "published",
  "anchor_state": "awaiting_cve",
  "title": "ESM import alias injection in happy-dom",
  "summary": "happy-dom before 21.0.4 may generate executable JavaScript from malformed ESM import aliases. Attackers who can provide HTML or module content can potentially run code as the Node.js process when JavaScript evaluation is enabled.",
  "mitigation": "Upgrade happy-dom to =>21.0.4 or later.",
  "vendor": "npm",
  "product": "npm:happy-dom",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 17.0.0, <= 21.0.3"
      ],
      "ecosystem": "npm",
      "fixed_versions": [
        "=>21.0.4"
      ],
      "package_name": "happy-dom",
      "purl": "pkg:npm/happy-dom"
    }
  ],
  "cwes": [
    94
  ],
  "cvss_score": 8.8,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 9.173769466666666,
  "t0_at": null,
  "signals": {
    "public_poc": {
      "at": "2026-10-20T18:13:05+00:00",
      "days": -0.3721225858217593,
      "is_lower_bound": true,
      "measured_at": "2026-10-21T03:08:56.448885+00:00",
      "url": "https://github.com/capricorn86/happy-dom/security/advisories/GHSA-834v-8h66-3h79"
    },
    "trigger_signal": {
      "at": "2026-10-20T18:13:05+00:00",
      "days": -0.3721225858217593,
      "is_lower_bound": true,
      "measured_at": "2026-10-21T03:08:56.448885+00:00",
      "url": "https://github.com/capricorn86/happy-dom/security/advisories/GHSA-834v-8h66-3h79"
    }
  }
}

published 2026-10-20 18:44Z
last change 2026-10-21 02:54Z

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.