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

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

GHSA-v96j-8cr9-jmvg ↗

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.
pip:turbohtml >= 1.1.0, < 1.15.11
fixed in 1.15.11
CWE-674 Uncontrolled Recursion
ETK-2026-4564Zero's internal tracking ID, independent of the CVE number., no cve assigned
pkg:pypi/turbohtml
2d 19h 12msince last run
15mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal +0dwaiting for further signals+0.0d
0
+1d
+2d
+3d

description

turbohtml XSD validation can exhaust the C stack when processing a crafted schema with deeply nested group-reference structures. An attacker can terminate the process if they can supply an XSD that the application compiles and later uses to validate a document.

mitigation

Upgrade turbohtml to version 1.15.11 or later. Until upgraded, do not compile or validate XSD schemas from untrusted sources.

fixed in 1.15.11

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.
–
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
15m
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

No artifact: an exploit or check was attempted but could not be produced at this moment.

source signals

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

  1. 2026-11-16 02:17Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-4564",
  "cve_id": null,
  "display_id": "ETK-2026-4564",
  "ghsa_id": "GHSA-v96j-8cr9-jmvg",
  "euvd_id": null,
  "status": "published",
  "anchor_state": "awaiting_cve",
  "title": "Stack exhaustion in turbohtml XSD validation",
  "summary": "turbohtml XSD validation can exhaust the C stack when processing a crafted schema with deeply nested group-reference structures. An attacker can terminate the process if they can supply an XSD that the application compiles and later uses to validate a document.",
  "mitigation": "Upgrade turbohtml to version 1.15.11 or later. Until upgraded, do not compile or validate XSD schemas from untrusted sources.",
  "vendor": "pip",
  "product": "pip:turbohtml",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 1.1.0, < 1.15.11"
      ],
      "ecosystem": "pip",
      "fixed_versions": [
        "1.15.11"
      ],
      "package_name": "turbohtml",
      "purl": "pkg:pypi/turbohtml"
    }
  ],
  "cwes": [
    674
  ],
  "cvss_score": 8.7,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 15.32009,
  "t0_at": null,
  "signals": {
    "trigger_signal": {
      "at": "2026-11-16T02:17:52+00:00",
      "days": -2.8138543703819443,
      "is_lower_bound": true,
      "measured_at": "2026-11-18T21:49:49.174011+00:00",
      "url": "https://github.com/tox-dev/turbohtml/security/advisories/GHSA-v96j-8cr9-jmvg"
    }
  }
}

published 2026-11-16 02:28Z
last change 2026-11-18 21:43Z

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.