Quick answers
- Is CVE-2026-8178 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-8178 being exploited in the wild.
- How severe is CVE-2026-8178?
- High severity, with a CVSS score of 8.1, published 8 May 2026.
- Which products and versions are affected?
- Amazon Redshift JDBC Driver < 2.2.2; com.amazon.redshift:redshift-jdbc42 (Maven) < 2.2.2, ECOSYSTEM:introduced=0,fixed=2.2.2.
- Is there a fix for CVE-2026-8178?
- Yes. com.amazon.redshift:redshift-jdbc42 (Maven): upgrade to 2.2.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-8178 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-8178?
- Check whether you run Amazon AWS, Amazon Redshift JDBC Driver or com.amazon.redshift:redshift-jdbc42 (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- com.amazon.redshift:redshift-jdbc42 (Maven): upgrade to 2.2.2 or later
# set com.amazon.redshift:redshift-jdbc42 to 2.2.2 in your pom.xml or build.gradle
Technical details
A remote code execution vulnerability exists in the Amazon Redshift JDBC Driver prior to version 2.2.2. The flaw stems from unsafe class loading during the processing of JDBC connection URL parameters. An attacker capable of influencing the connection string—such as through a web application that allows user-defined database connections—can trigger the driver to load and execute arbitrary Java classes. This occurs within the security context of the application using the driver. The issue is resolved in version 2.2.2.
Affected products
- Amazon Redshift JDBC Driver < 2.2.2
Identifiers
- CVE-2026-8178
- GHSA-wmmv-vvg5-993q
Timeline
- 2026-05-08: disclosed
- 2026-05-08: patched: Fixed in version 2.2.2