Arbitrary Code Injection Affecting redshift-connector package, versions [,2.1.14)
Threat Intelligence
This vulnerability is trending on Twitter; this may indicate a growing threat.
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Arbitrary Code Injection vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-PYTHON-REDSHIFTCONNECTOR-17111071
- published31 May 2026
- disclosed29 May 2026
- creditKexin Chen
Introduced: 29 May 2026
CVE-2026-8838 (opens in a new tab)How to fix?
Upgrade redshift-connector to version 2.1.14 or higher.
Overview
redshift-connector is a Redshift interface library
Affected versions of this package are vulnerable to Arbitrary Code Injection due to the use of eval() on untrusted data received from the server, in the vector_in() function. An attacker can execute arbitrary code on the client system by sending malicious query responses.
If the attacker is in a MitM position, it lowers the likelihood of a successful attack (CVSS AT:P). But an attacker on the internet in control of a rogue server who can convince a client to send requests to it is also able to exploit this vulnerability, so it is assessed here as AV:N with UI:P.