CVE-2026-8838

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 0.8%, top 48% 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.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 9.8Exploit: NoneExposed: 0

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

Unsafe use of Python's eval() on server-received data in the vector_in() function in amazon-redshift-python-driver before 2.1.14 allows a rogue server or man-in-the-middle actor to execute arbitrary code on the client.

To remediate this issue, users should upgrade to version 2.1.14.

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

Published

May 18, 2026

Last Modified

May 19, 2026

Advisory Details (3)

Auto-updated Jun 21, 2026
Patch available. Sources: github_release, github.
github Patch Available

Remote Code Execution via eval() Injection in amazon-redshift-python-driver · Advisory · aws/amazon-redshift-python-driver · GitHub

https://github.com/aws/amazon-redshift-python-driver/security/advisories/GHSA-29h4-r29x-hchv
github_release Patch Available

v2.1.14

Patch available: aws/amazon-redshift-python-driver v2.1.14

https://github.com/aws/amazon-redshift-python-driver/releases/tag/v2.1.14
generic

CVE-2026-8838 - Remote Code Execution in amazon-redshift-python-driver

https://aws.amazon.com/security/security-bulletins/2026-033-aws/

Vendor Advisories for CVE-2026-8838(2)

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

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
redshift-connector2.0.384 ... 2.1.9 (58 versions)2.1.14—

Weakness Classification(1)

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

Data Freshness Timeline

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

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-8838?
CVE-2026-8838 is a critical vulnerability published on May 18, 2026. Unsafe use of Python's eval() on server-received data in the vector_in() function in amazon-redshift-python-driver before 2.1.14 allows a rogue server or man-in-the-middle actor to execute arbitrary code on the client. To remediate this issue, users should upgrade to version 2.1.14.
When was CVE-2026-8838 disclosed?
CVE-2026-8838 was first published in the National Vulnerability Database on May 18, 2026, with the most recent update on May 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-8838 actively exploited?
CVE-2026-8838 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 52.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-8838?
CVE-2026-8838 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-8838?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-8838, 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-8838

Explore →

Is Your Infrastructure Affected by CVE-2026-8838?

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

Start Free Scan →Browse All CVEs