Skip to main content
Public proof of conceptFix availableAwaiting NVD analysis

CVE-2026-8838

A public proof of concept exists; no exploitation attested.

  • Published2026-05-18
  • Fixed in2.1.14
  • WeaknessCWE-94

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

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.

Timeline

dates in UTC
  1. 2026-05-1821:16CVE publishedNVD

Versions per branch

OSV
redshift-connector
BranchAffectedFixed in
2.1< 2.1.142.1.14

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA1 product

As AMZN, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • AWS Amazon Redshift connector for Pythonother versions: not affected
    Affected
    • ≤ 2.1.13no fix statedcustom

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2026-05-18

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • airflow-2CleanStartall versions · fixed in 2.11.2-r2
  • airflow-2Chainguardall versions · no fixed version listed
  • airflow-3Wolfiall versions · fixed in 3.2.1-r4
  • airflow-3MinimOSall versions · fixed in 3.2.2-r0
  • airflow-3CleanStartall versions · fixed in 3.2.0-r0
  • airflow-3CleanStartall versions · fixed in 3.1.8-r2
  • airflow-3CleanStartall versions · fixed in 3.2.0-r1
  • airflow-3Chainguardall versions · fixed in 3.2.1-r4

2 more package ranges on OSV.dev

Full record on NVD

Fix

  1. Update redshift-connector to 2.1.14

Detection

read 2026-11-01 01:02 UTC
Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

  • NVDCVE recordread 2026-10-23
  • CISA-ADPSSVC decisionnone2026-05-19
  • CNACVSS 4.09.3known since 2026-10-23
  • CNACVSS 3.19.8known since 2026-10-23
  • CNAweakness (CWE)CWE-94known since 2026-10-23
  • FIRST EPSSEPSS score0.8 %2026-11-09
  • PoC-in-GitHubproof of concept2known since 2026-11-01
  • OSVaffected packages—
  • GitHub AdvisoriesadvisoryCRITICAL2026-05-29

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CVSS 4.0 vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Published
2026-05-18
Last Modified
2026-07-23
NVD status
Awaiting Analysis
GitHub Advisory
GHSA-29h4-r29x-hchv

Frequently asked questions

What is CVE-2026-8838?

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.

Is CVE-2026-8838 actively exploited?

Active exploitation of CVE-2026-8838 has not been confirmed. Its EPSS score was 0.8% on 2026-11-09, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2026-8838?

CVE-2026-8838 has a CVSS v3 base score of 9.8 (CRITICAL severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.

Running mageai? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month

Sources for this record