CVE-2026-27965

CRITICALNVD 9.99.9
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.9 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 65% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
9.9EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.9Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.9(medium)
EG Risk
49(Track)
EG Risk 49/100SSVC: Track

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
Severity99% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
36%
KEV
Not listed

Published

February 26, 2026

Last Modified

June 17, 2026

Advisory Details (4)

Auto-updated Sep 14, 2026
Patch available. Sources: github_commit, github_pr, github.
github Patch Available

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_pr

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
generic

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
govitess.io/vitessghsa

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 rangeFixed inDependents
vitess.io/vitess0.23.3

Weakness Classification(1)

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

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

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

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 104 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-27965?
CVE-2026-27965 is a critical vulnerability 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 CVE-2026-27965 disclosed?
CVE-2026-27965 was first published in the National Vulnerability Database on February 26, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-27965 actively exploited?
CVE-2026-27965 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 64.3% of all 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?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-27965, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

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.