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

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

GHSA-f4vg-frjx-6j7w ↗

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.0.0, <= 1.13.1
fixed in 1.14.0
CWE-787 Out-of-bounds Write
ETK-2026-1233Zero's internal tracking ID, independent of the CVE number., no cve assigned
pkg:pypi/turbohtml
9d 18h 26msince last run
39mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal +0dwaiting for further signals+1.6d
0
+5d
+10d

description

turbohtml table-to-text and table-to-Markdown rendering can write beyond a heap buffer when tables contain deeply nested row groups. An attacker who can supply markup parsed as a fragment or XML and cause the resulting DOM to be rendered may crash the process or corrupt adjacent memory.

mitigation

Upgrade pip package turbohtml to version 1.14.0 or later. Until upgraded, do not render untrusted fragment- or XML-derived markup to text or Markdown.

fixed in 1.14.0

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
39m
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-10-09 21:11Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-1233",
  "cve_id": null,
  "display_id": "ETK-2026-1233",
  "ghsa_id": "GHSA-f4vg-frjx-6j7w",
  "euvd_id": null,
  "status": "published",
  "anchor_state": "awaiting_cve",
  "title": "Heap buffer overflow in turbohtml table rendering",
  "summary": "turbohtml table-to-text and table-to-Markdown rendering can write beyond a heap buffer when tables contain deeply nested row groups. An attacker who can supply markup parsed as a fragment or XML and cause the resulting DOM to be rendered may crash the process or corrupt adjacent memory.",
  "mitigation": "Upgrade pip package turbohtml to version 1.14.0 or later. Until upgraded, do not render untrusted fragment- or XML-derived markup to text or Markdown.",
  "vendor": "pip",
  "product": "pip:turbohtml",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 1.0.0, <= 1.13.1"
      ],
      "ecosystem": "pip",
      "fixed_versions": [
        "1.14.0"
      ],
      "package_name": "turbohtml",
      "purl": "pkg:pypi/turbohtml"
    }
  ],
  "cwes": [
    787
  ],
  "cvss_score": 8.2,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 38.86503458333333,
  "t0_at": null,
  "signals": {
    "trigger_signal": {
      "at": "2026-10-09T21:11:43+00:00",
      "days": -11.319242308692129,
      "is_lower_bound": true,
      "measured_at": "2026-10-21T04:51:25.558186+00:00",
      "url": "https://github.com/tox-dev/turbohtml/security/advisories/GHSA-f4vg-frjx-6j7w"
    }
  }
}

published 2026-10-11 09:46Z
last change 2026-10-21 04: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.