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

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

GHSA-m4cr-m4qc-9hh3 ↗

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:pydantic-ai-harness >= 0.4.0, <= 0.69.0
fixed in 0.70.0
CWE-1333 Inefficient Regular Expression Complexity
ETK-2026-4763Zero's internal tracking ID, independent of the CVE number., no cve assigned
pkg:pypi/pydantic-ai-harness
14h 44msince last run
16mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal +0hwaiting for further signals+7h01m
0
+12h
+18h
+24h

description

pydantic-ai-harness is affected when ToolOutputLimits enables strip_ansi. An attacker who can influence tool-returned content may cause excessive event-loop work and delay other application activity.

mitigation

Upgrade pydantic-ai-harness to 0.70.0 or later. Until upgraded, disable strip_ansi; deployments on Pydantic AI v1 should move to Pydantic AI v2 before upgrading the harness.

fixed in 0.70.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.
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-11-18 00:04Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-4763",
  "cve_id": null,
  "display_id": "ETK-2026-4763",
  "ghsa_id": "GHSA-m4cr-m4qc-9hh3",
  "euvd_id": null,
  "status": "published",
  "anchor_state": "awaiting_cve",
  "title": "Quadratic denial of service in pydantic-ai-harness ANSI stripping",
  "summary": "pydantic-ai-harness is affected when `ToolOutputLimits` enables `strip_ansi`. An attacker who can influence tool-returned content may cause excessive event-loop work and delay other application activity.",
  "mitigation": "Upgrade pydantic-ai-harness to 0.70.0 or later. Until upgraded, disable `strip_ansi`; deployments on Pydantic AI v1 should move to Pydantic AI v2 before upgrading the harness.",
  "vendor": "pip",
  "product": "pip:pydantic-ai-harness",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0.4.0, <= 0.69.0"
      ],
      "ecosystem": "pip",
      "fixed_versions": [
        "0.70.0"
      ],
      "package_name": "pydantic-ai-harness",
      "purl": "pkg:pypi/pydantic-ai-harness"
    }
  ],
  "cwes": [
    1333
  ],
  "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": 16.26774045,
  "t0_at": null,
  "signals": {
    "trigger_signal": {
      "at": "2026-11-18T00:04:44+00:00",
      "days": -0.9064409001041667,
      "is_lower_bound": true,
      "measured_at": "2026-11-18T21:50:00.541672+00:00",
      "url": "https://github.com/pydantic/pydantic-ai/security/advisories/GHSA-m4cr-m4qc-9hh3"
    }
  }
}

published 2026-11-18 06:55Z
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.