CVE-2026-27965

CRITICALNVD 9.99.9
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.9 under NVD CVSS v3. EPSS exploit probability: 0.5% (41st percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Trending — 4 sources updated this weekElevated

Also known asEUVD-2026-8818 (ENISA EUVD) · GHSA-8g8j-r87h-p36x (GitHub Security Advisories)Source: ENISA EUVD

9.9EG
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).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 9.9Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Vitess is a database clustering system for horizontal scaling of MySQL. Prior to versions 23.0.3 and 22.0.4, anyone with read/write access to the backup storage location (e.g. an S3 bucket) can manipulate backup manifest files so that arbitrary code is later executed when that backup is restored. This can be used to provide that attacker with unintended/unauthorized access to the production deployment environment — allowing them to access information available in that environment as well as run any additional arbitrary commands there. Versions 23.0.3 and 22.0.4 contain a patch. Some workarounds are available. Those who intended to use an external decompressor then can always specify that decompressor command in the --external-decompressor flag value for vttablet and vtbackup. That then overrides any value specified in the manifest file. Those who did not intend to use an external decompressor, nor an internal one, can specify a value such as cat or tee in the --external-decompressor flag value for vttablet and vtbackup to ensure that a harmless command is always used.

CVSS v3
9.9
EG Score
9.9CRITICALmedium confidence
EG Risk
61
EG Risk 61/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)
Severity99% × 45%
Impact severity (EG Severity): CVSS 9.9 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
41st
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 (9.9): severity, escalated by confirmed exploitation. This CVE's 9.9 is its impact severity (EG Severity), not escalated.

EG Severity
9.9 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). 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, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade 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, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (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

February 26, 2026

Last Modified

June 17, 2026

Advisory Details (4)

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

Users with backup storage access can gain unauthorized access to production deployment environments · Advisory · vitessio/vitess · GitHub

https://github.com/vitessio/vitess/security/advisories/GHSA-8g8j-r87h-p36x
GitHub pull request

Restore: make loading compressor commands from `MANIFEST` opt-in

Fix merged in vitessio/vitess PR #19460 on 2026-02-24 — awaiting tagged release

https://github.com/vitessio/vitess/pull/19460
Web page

Bug Report: backup restore trusts decompressor in `MANIFEST` by default · Issue #19459 · vitessio/vitess · GitHub

https://github.com/vitessio/vitess/issues/19459
GitHub commit

commit 4c0173293907 (vitessio/vitess)

Fix landed in vitessio/vitess commit 4c0173293907 — awaiting tagged release

https://github.com/vitessio/vitess/commit/4c0173293907af9cb942a6683c465c3f1e9fdb5c

Vendor Advisories for CVE-2026-27965(1)

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
govitess.io/vitess—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFix by version rangeDependents
vitess.io/vitess—
  • every version through 0.23.2: no fix on record
  • every version up to 0.22.4: fixed in 0.22.4
  • 0.23.0 up to 0.23.3: fixed in 0.23.3
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 22× in last 7d / 90× 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.

Showing the most recent 98 of 200 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 2 repeat rows among the latest 100 are merged into the row they repeat. The 102 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  2. 2026-11-01 14:25 UTCEG score recompute
  3. 2026-11-01 14:25 UTCVendor advisory
  4. 2026-11-01 14:25 UTCGHSA enrichmentGHSA-8g8j-r87h-p36x · GitHub severity HIGH
  5. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  6. 2026-10-31 13:40 UTCEG score recompute
  7. 2026-10-31 13:40 UTCVendor advisory
  8. 2026-10-31 13:39 UTCGHSA enrichmentGHSA-8g8j-r87h-p36x · GitHub severity HIGH
  9. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  10. 2026-10-30 12:53 UTCEG score recompute
  11. 2026-10-30 12:53 UTCVendor advisory
  12. 2026-10-30 12:53 UTCGHSA enrichmentGHSA-8g8j-r87h-p36x · GitHub severity HIGH
  13. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  14. 2026-10-29 12:05 UTCEG score recompute
  15. 2026-10-29 12:05 UTCGHSA enrichmentGHSA-8g8j-r87h-p36x · GitHub severity HIGH
  16. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  17. 2026-10-28 11:11 UTCEG score recompute
  18. 2026-10-28 11:11 UTCGHSA enrichmentGHSA-8g8j-r87h-p36x · GitHub severity HIGH
  19. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  20. 2026-10-27 09:44 UTCEG score recompute
  21. 2026-10-27 09:44 UTCGHSA enrichmentGHSA-8g8j-r87h-p36x · GitHub severity HIGH
  22. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  23. 2026-10-26 08:58 UTCEG score recompute
  24. 2026-10-26 08:58 UTCGHSA enrichmentGHSA-8g8j-r87h-p36x · GitHub severity HIGH
  25. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.5% · 40th percentile
Show 73 more
  1. 2026-10-25 14:38 UTCEG score recompute
  2. 2026-10-25 08:13 UTCEG score recompute
  3. 2026-10-25 08:13 UTCVendor advisory
  4. 2026-10-25 08:13 UTCGHSA enrichmentGHSA-8g8j-r87h-p36x · GitHub severity HIGH
  5. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  6. 2026-10-24 07:27 UTCEG score recompute
  7. 2026-10-24 07:27 UTCGHSA enrichmentGHSA-8g8j-r87h-p36x · GitHub severity HIGH
  8. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  9. 2026-10-23 06:41 UTCEG score recompute
  10. 2026-10-23 06:41 UTCVendor advisory
  11. 2026-10-23 06:41 UTCGHSA enrichmentGHSA-8g8j-r87h-p36x · GitHub severity HIGH
  12. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  13. 2026-10-22 05:54 UTCEG score recompute
  14. 2026-10-22 05:54 UTCVendor advisory
  15. 2026-10-22 05:54 UTCGHSA enrichmentGHSA-8g8j-r87h-p36x · GitHub severity HIGH
  16. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  17. 2026-10-21 05:08 UTCEG score recompute
  18. 2026-10-21 05:08 UTCVendor advisory
  19. 2026-10-21 05:08 UTCGHSA enrichmentGHSA-8g8j-r87h-p36x · GitHub severity HIGH
  20. 2026-10-20 16:32 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  21. 2026-10-20 04:21 UTCEG score recompute
  22. 2026-10-20 04:21 UTCVendor advisory
  23. 2026-10-20 04:21 UTCGHSA enrichmentGHSA-8g8j-r87h-p36x · GitHub severity HIGH
  24. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  25. 2026-10-19 03:34 UTCEG score recompute
  26. 2026-10-19 03:34 UTCVendor advisory
  27. 2026-10-19 03:34 UTCGHSA enrichmentGHSA-8g8j-r87h-p36x · GitHub severity HIGH
  28. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  29. 2026-10-18 03:50 UTCEG score recompute
  30. 2026-10-18 02:47 UTCEG score recompute
  31. 2026-10-18 02:47 UTCVendor advisory
  32. 2026-10-18 02:46 UTCGHSA enrichmentGHSA-8g8j-r87h-p36x · GitHub severity HIGH
  33. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  34. 2026-10-17 01:59 UTCEG score recompute
  35. 2026-10-17 01:59 UTCGHSA enrichmentGHSA-8g8j-r87h-p36x · GitHub severity HIGH
  36. 2026-10-16 16:41 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  37. 2026-10-16 01:10 UTCEG score recompute
  38. 2026-10-16 01:09 UTCGHSA enrichmentGHSA-8g8j-r87h-p36x · GitHub severity HIGH
  39. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  40. 2026-10-14 20:14 UTCEG score recompute
  41. 2026-10-14 20:14 UTCGHSA enrichmentGHSA-8g8j-r87h-p36x · GitHub severity HIGH
  42. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  43. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  44. 2026-10-13 16:24 UTCEG score recompute
  45. 2026-10-13 16:24 UTCVendor advisory
  46. 2026-10-13 16:24 UTCGHSA enrichmentGHSA-8g8j-r87h-p36x · GitHub severity HIGH
  47. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  48. 2026-10-12 15:37 UTCEG score recompute
  49. 2026-10-12 15:37 UTCVendor advisory
  50. 2026-10-12 15:37 UTCGHSA enrichmentGHSA-8g8j-r87h-p36x · GitHub severity HIGH
  51. 2026-10-12 08:48 UTCVendor advisory
  52. 2026-10-12 08:48 UTCGHSA enrichmentGHSA-8g8j-r87h-p36x · GitHub severity HIGH
  53. 2026-10-11 19:59 UTCEG score recompute
  54. 2026-10-11 17:12 UTCEG score recompute
  55. 2026-10-11 14:43 UTCEG score recompute
  56. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  57. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  58. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  59. 2026-10-09 14:28 UTCOSV refresh
  60. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  61. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  62. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  63. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  64. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  65. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  66. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  67. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  68. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  69. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  70. 2026-09-26 00:26 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  71. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  72. 2026-09-19 21:50 UTCOSV refresh
  73. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.4% · 35th percentile

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-27965?
CVE-2026-27965 is a critical-severity vulnerability; its CVE record was published on February 26, 2026. Vitess is a database clustering system for horizontal scaling of MySQL. Prior to versions 23.0.3 and 22.0.4, anyone with read/write access to the backup storage location (e.g. an S3 bucket) can manipulate backup manifest files so that arbitrary code is later executed when that backup is restored.…
When was the CVE record for CVE-2026-27965 published?
The CVE record for CVE-2026-27965 was published on February 26, 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 June 17, 2026; the record at its source may have been updated since.
Is CVE-2026-27965 actively exploited?
CVE-2026-27965 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (41st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-27965?
CVE-2026-27965 has a CVSS v3 base score of 9.9 (NVD).
How do I remediate CVE-2026-27965?
A fix for CVE-2026-27965 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-27965 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-27965

Explore →

Is Your Infrastructure Affected by CVE-2026-27965?

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

Book a Demo →Browse All CVEs