CVE-2026-48773

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 72% 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, secondary
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 9.8Exploit: NoneExposed: 0

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

ProxySQL is a proxy for MySQL and its forks, as well as PostgreSQL. Versions 2.0.18 through 3.0.8 have a pre-authentication heap memory corruption vulnerability in the MySQL and PostgreSQL protocol first-read paths. A remote unauthenticated client can declare an oversized first packet length, and ProxySQL passes that attacker-controlled length directly to recv() while writing into a fixed 32 KB input queue. Version 3.0.9 patches the issue.

CVSS v3
9.8
EG Score
9.8(medium)
EPSS
28.0%
KEV
Not listed

Published

June 19, 2026

Last Modified

June 23, 2026

Advisory Details (2)

Auto-updated Jul 12, 2026
🔬 Proof of concept available. Patch available. Sources: github_release, github.
github Patch Available🟡 PoC Available

ProxySQL pre-auth heap overflow in MySQL and PostgreSQL first-packet handling · Advisory · sysown/proxysql · GitHub

https://github.com/sysown/proxysql/security/advisories/GHSA-58ww-865x-grpr
github_release Patch Available

ProxySQL 3.0.9

Patch available: sysown/proxysql v3.0.9

https://github.com/sysown/proxysql/releases/tag/v3.0.9

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 45× in last 7d / 167× 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 167 total refreshes for this CVE.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-48773?
CVE-2026-48773 is a critical vulnerability published on June 19, 2026. ProxySQL is a proxy for MySQL and its forks, as well as PostgreSQL. Versions 2.0.18 through 3.0.8 have a pre-authentication heap memory corruption vulnerability in the MySQL and PostgreSQL protocol first-read paths. A remote unauthenticated client can declare an oversized first packet length, and…
When was CVE-2026-48773 disclosed?
CVE-2026-48773 was first published in the National Vulnerability Database on June 19, 2026, with the most recent update on June 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-48773 actively exploited?
CVE-2026-48773 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 28.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-48773?
CVE-2026-48773 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-48773?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-48773, 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

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

Explore →

Is Your Infrastructure Affected by CVE-2026-48773?

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

Start Free Scan →Browse All CVEs