CVE-2019-2822

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2022-05-24. NVD baseline CVSS 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 3%CVSS: 7.5Exploit: NoneExposed: 0

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

Vulnerability in the MySQL Server component of Oracle MySQL (subcomponent: Shell: Admin / InnoDB Cluster). Supported versions that are affected are 8.0.16 and prior. Difficult to exploit vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in takeover of MySQL Server. CVSS 3.0 Base Score 7.5 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H).

CVSS v3
7.5
EG Score
7.5(medium)
EPSS
84.8%
KEV
Not listed

Published

July 23, 2019

Last Modified

November 21, 2024

References (6)

Data Freshness Timeline

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

  1. 2026-07-06 16:25 UTCEPSS rescore
  2. 2026-07-06 16:25 UTCEPSS rescore
  3. 2026-07-06 02:20 UTCEPSS rescore
  4. 2026-07-06 02:20 UTCEPSS rescore
  5. 2026-07-05 02:27 UTCEPSS rescore
  6. 2026-07-04 06:28 UTCEPSS rescore
  7. 2026-07-03 07:26 UTCOSV refresh
  8. 2026-07-01 15:03 UTCEPSS rescore
  9. 2026-07-01 15:03 UTCEPSS rescore
  10. 2026-06-30 23:20 UTCEPSS rescore
  11. 2026-06-29 14:03 UTCEPSS rescore
  12. 2026-06-28 14:04 UTCEPSS rescore
  13. 2026-06-28 04:54 UTCEPSS rescore
  14. 2026-06-28 04:54 UTCEPSS rescore
  15. 2026-06-27 03:06 UTCEPSS rescore
  16. 2026-06-25 13:47 UTCEPSS rescore
  17. 2026-06-25 13:47 UTCEPSS rescore
  18. 2026-06-24 14:03 UTCEPSS rescore
  19. 2026-06-24 14:03 UTCEPSS rescore
  20. 2026-06-23 21:31 UTCEPSS rescore
  21. 2026-06-23 21:31 UTCEPSS rescore
  22. 2026-06-22 14:23 UTCEPSS rescore
  23. 2026-06-22 14:23 UTCEPSS rescore
  24. 2026-06-21 01:57 UTCEPSS rescore
  25. 2026-06-21 01:57 UTCEPSS rescore
Show 45 more
  1. 2026-06-19 19:23 UTCEPSS rescore
  2. 2026-06-19 19:23 UTCEPSS rescore
  3. 2026-06-18 17:50 UTCEPSS rescore
  4. 2026-06-18 17:50 UTCEPSS rescore
  5. 2026-06-17 17:50 UTCEPSS rescore
  6. 2026-06-16 17:50 UTCEPSS rescore
  7. 2026-06-15 17:46 UTCEPSS rescore
  8. 2026-06-14 23:15 UTCEPSS rescore
  9. 2026-06-14 23:15 UTCEPSS rescore
  10. 2026-06-14 22:13 UTCOSV refresh
  11. 2026-06-13 22:58 UTCEPSS rescore
  12. 2026-06-12 23:09 UTCEPSS rescore
  13. 2026-06-12 23:09 UTCEPSS rescore
  14. 2026-06-11 13:58 UTCEPSS rescore
  15. 2026-06-10 22:16 UTCEPSS rescore
  16. 2026-06-10 22:16 UTCEPSS rescore
  17. 2026-06-10 13:19 UTCEPSS rescore
  18. 2026-06-08 14:15 UTCEPSS rescore
  19. 2026-06-08 14:15 UTCEPSS rescore
  20. 2026-06-08 14:15 UTCEPSS rescore
  21. 2026-06-07 15:23 UTCEPSS rescore
  22. 2026-06-07 15:23 UTCEPSS rescore
  23. 2026-06-06 13:45 UTCEPSS rescore
  24. 2026-06-06 13:45 UTCEPSS rescore
  25. 2026-06-05 22:45 UTCEPSS rescore
  26. 2026-06-05 06:08 UTCEPSS rescore
  27. 2026-06-04 13:10 UTCEPSS rescore
  28. 2026-06-04 13:10 UTCEPSS rescore
  29. 2026-06-02 20:11 UTCEPSS rescore
  30. 2026-06-02 20:11 UTCEPSS rescore
  31. 2026-05-31 22:29 UTCEPSS rescore
  32. 2026-05-31 22:29 UTCEPSS rescore
  33. 2026-05-31 00:14 UTCEPSS rescore
  34. 2026-05-31 00:14 UTCEPSS rescore
  35. 2026-05-29 13:42 UTCEPSS rescore
  36. 2026-05-28 13:43 UTCEPSS rescore
  37. 2026-05-28 13:43 UTCEPSS rescore
  38. 2026-05-27 16:57 UTCEG score recompute
  39. 2026-05-27 16:57 UTCGHSA enrichment
  40. 2026-05-27 13:39 UTCEPSS rescore
  41. 2026-05-27 13:38 UTCEPSS rescore
  42. 2026-05-26 07:17 UTCEPSS rescore
  43. 2026-05-26 07:17 UTCEPSS rescore
  44. 2026-05-26 07:17 UTCEPSS rescore
  45. 2026-05-24 16:47 UTCEPSS rescore

Frequently asked(5)

What is CVE-2019-2822?
CVE-2019-2822 is a high vulnerability published on July 23, 2019. Vulnerability in the MySQL Server component of Oracle MySQL (subcomponent: Shell: Admin / InnoDB Cluster). Supported versions that are affected are 8.0.16 and prior. Difficult to exploit vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise MySQL…
When was CVE-2019-2822 disclosed?
CVE-2019-2822 was first published in the National Vulnerability Database on July 23, 2019, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2019-2822 actively exploited?
CVE-2019-2822 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 84.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2019-2822?
CVE-2019-2822 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2019-2822?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-2822, 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-2019-2822

Explore →

Is Your Infrastructure Affected by CVE-2019-2822?

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

Start Free Scan →Browse All CVEs