CVE-2026-104252

CRITICALPre-NVD 9.89.8
EchelonGraph scoreLOW confidence

This critical-severity CVE scores 9.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: a secondary CVSS source
9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: —CVSS: 9.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Vitess is a database clustering system for horizontal scaling of MySQL. Prior to 23.0.5 and 24.0.2, twopczHandler in go/vt/vttablet/tabletserver/twopcz.go writes the Action and dtid form values from the vttablet and vtcombo /twopcz HTTP debug endpoint into a text/html response without HTML escaping. Under the default allow-all ACL policy, a remote unauthenticated attacker can send an operator a crafted request that executes script in the operator's browser after the request is opened. The script runs with the vttablet debug origin and can read same-origin diagnostic endpoints that expose query, transaction, environment, variable, or profiling data available in that deployment. This issue is fixed in versions 23.0.5 and 24.0.2.

CVSS v3
9.8
EG Score
9.8CRITICALlow confidence
EG Risk
44
EG Risk 44/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
The EG Score, 9.8 of 10.
Exploitation0% × 40%
No KEV listing, EG-KEV tier or EPSS when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
—
EPSS %ILE
—
KEV
Not listed

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

A fix is available. Apply it within your standard update timelines.

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” 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

October 13, 2026

Last Modified

October 13, 2026

Advisory Details (9)

Auto-updated Oct 14, 2026
Patch available. Sources: github_commit, github_pr, github_release, github.
GitHub advisoryMentions a patch (unverified)

Vitess vttablet /twopcz reflected XSS · Advisory · vitessio/vitess · GitHub

Affected: v23.0.5 and v24.0.2 (

https://github.com/vitessio/vitess/security/advisories/GHSA-v75v-6fpf-gvw8
GitHub release Patch Available

Vitess v24.0.2

Patch available: vitessio/vitess v24.0.2

https://github.com/vitessio/vitess/releases/tag/v24.0.2
GitHub release Patch Available

Vitess v23.0.5

Patch available: vitessio/vitess v23.0.5

https://github.com/vitessio/vitess/releases/tag/v23.0.5
GitHub pull request

[release-24.0] tabletserver: escape reflected form values in twopcz handler (#20255)

Fix merged in vitessio/vitess PR #20274 on 2026-06-09 — awaiting tagged release

https://github.com/vitessio/vitess/pull/20274
GitHub pull request

[release-23.0] tabletserver: escape reflected form values in twopcz handler (#20255)

Fix merged in vitessio/vitess PR #20273 on 2026-06-09 — awaiting tagged release

https://github.com/vitessio/vitess/pull/20273
GitHub pull request

tabletserver: escape reflected form values in twopcz handler

Fix merged in vitessio/vitess PR #20255 on 2026-06-09 — awaiting tagged release

https://github.com/vitessio/vitess/pull/20255
GitHub commit

commit c1ed96302e65 (vitessio/vitess)

Fix landed in vitessio/vitess commit c1ed96302e65 — awaiting tagged release

https://github.com/vitessio/vitess/commit/c1ed96302e658190168c971afdac730cf70e43f7
GitHub commit

commit 976e1e0d78f9 (vitessio/vitess)

Fix landed in vitessio/vitess commit 976e1e0d78f9 — awaiting tagged release

https://github.com/vitessio/vitess/commit/976e1e0d78f9d29d02e5e31b4aa7e180648f08af
GitHub commit

commit 3140c1846cd1 (vitessio/vitess)

Fix landed in vitessio/vitess commit 3140c1846cd1 — awaiting tagged release

https://github.com/vitessio/vitess/commit/3140c1846cd120db34f33b2083139b4ab638aed2

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 3× in last 7d / 3× 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 it from the CNA feed. 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). Most recent first.

  1. 2026-10-13 20:26 UTCEG score recompute
  2. 2026-10-13 19:36 UTCEG score recomputeFirst assessed: 9.8 CRITICAL
  3. 2026-10-13 19:34 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-104252?
CVE-2026-104252 is a critical-severity vulnerability; its CVE record was published on October 13, 2026. Vitess is a database clustering system for horizontal scaling of MySQL. Prior to 23.0.5 and 24.0.2, twopczHandler in go/vt/vttablet/tabletserver/twopcz.go writes the Action and dtid form values from the vttablet and vtcombo /twopcz HTTP debug endpoint into a text/html response without HTML…
When was the CVE record for CVE-2026-104252 published?
The CVE record for CVE-2026-104252 was published on October 13, 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 October 13, 2026; the record at its source may have been updated since.
What is the CVSS score of CVE-2026-104252?
CVE-2026-104252 has a CVSS base score of 9.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-104252?
A fix for CVE-2026-104252 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-104252?

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