CVE-2026-133161

HIGHPre-NVD 7.57.5
EchelonGraph scoreHIGH confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-11-19. A secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: GitHub Security Advisory, a secondary CVSS source

Also known asEUVD-2026-130213 (ENISA EUVD) · GHSA-wvp9-4g4g-qwgm (GitHub Security Advisories)Source: ENISA EUVD

7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 7.5Exploit: None knownExposed services: Not assessed

The CVE record names the fixed release — apply it.

Summary ui

With strip_ansi=True, Pydantic AI Harness's ToolOutputLimits capability removes ANSI escape sequences from tool output with a pattern that takes time quadratic in the length of a line. A tool result of a few hundred kilobytes, crafted with many unterminated escape sequences, can occupy the event loop for tens of seconds to minutes, delaying every other request and agent run in the process.

Details

This affects applications that set strip_ansi=True on ToolOutputLimits (named OverflowingToolOutput before 0.13.0) and run tools whose output an attacker can influence, such as shell commands, file reads, fetched pages or MCP servers. Stripping runs on the event loop before the capability reduces the output, so its own size limits do not bound it.

The assumed attacker can place text in content a tool returns.

Mitigation

Upgrade pydantic-ai-harness to 0.70.0 or later. Until then, leave strip_ansi at its default, False.

On Pydantic AI v1, the harness cannot be upgraded past 0.4.0. Upgrade to Pydantic AI v2 and pydantic-ai-harness 0.70.0, or leave strip_ansi off.

CVSS v3
7.5
EG Score
7.5HIGHhigh confidence
EG Risk
49
EG Risk 49/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0% × 40%
No KEV listing, EG-KEV tier or EPSS when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: The CVE record names the fixed release. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
36th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

The CVE record names the fixed release. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

November 19, 2026

Last Modified

November 19, 2026

Advisory Details (1)

Auto-updated Nov 19, 2026
Fix named in the CVE record. Sources: github.
GitHub advisoryMentions a patch (unverified)

Harness `ToolOutputLimits` ANSI stripping can take quadratic time, blocking the event loop · Advisory · pydantic/pydantic-ai · GitHub

https://github.com/pydantic/pydantic-ai/security/advisories/GHSA-m4cr-m4qc-9hh3

Vendor Advisories for CVE-2026-133161(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 5× in last 7d / 5× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-21 16:38 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  2. 2026-11-20 16:36 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  3. 2026-11-19 16:03 UTCENISA EUVD ID recordedEUVD-2026-130213 · Source: ENISA EUVD
  4. 2026-11-19 15:46 UTCEchelonGraph re-scored
  5. 2026-11-19 15:46 UTCGHSA enrichmentGHSA-wvp9-4g4g-qwgm · GitHub severity HIGH · GitHub CVSS 7.5
  6. 2026-11-19 15:28 UTCEchelonGraph re-scored
  7. 2026-11-19 14:49 UTCEchelonGraph re-scored
  8. 2026-11-19 14:24 UTCEchelonGraph re-scoredFirst assessed: 7.5 HIGH
  9. 2026-11-19 14:22 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-133161?
CVE-2026-133161 is a high-severity vulnerability; its CVE record was published on November 19, 2026. Summary ui With strip_ansi=True, Pydantic AI Harness's ToolOutputLimits capability removes ANSI escape sequences from tool output with a pattern that takes time quadratic in the length of a line. A tool result of a few hundred kilobytes, crafted with many unterminated escape sequences, can occupy…
When was the CVE record for CVE-2026-133161 published?
The CVE record for CVE-2026-133161 was published on November 19, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 19, 2026; the record at its source may have been updated since.
Is CVE-2026-133161 actively exploited?
CVE-2026-133161 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (36th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-133161?
CVE-2026-133161 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-133161?
The CVE record for CVE-2026-133161 names the fix: "Upgrade `pydantic-ai-harness` to 0.70.0 or later." The vendor advisories EchelonGraph has for CVE-2026-133161 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-133161

Explore →

Is Your Infrastructure Affected by CVE-2026-133161?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.