CVE-2026-8178: Remote Code Execution via Unsafe Class Loading in Amazon Redshift JDBC Driver
Summary Amazon Redshift JDBC Driver is a Type 4 JDBC driver that provides database connectivity through the standard JDBC application program interfaces (APIs). An issue exists in versions prior to 2.2.2 where the driver could load arbitrary classes when processing certain connection URL parameters, potentially allowing code execution in the application context.
Impact When a JDBC connection URL contains certain parameters, the driver processes the parameter values in a way that could trigger the execution of code from classes available on the application's classpath. An actor who can influence the JDBC connection URL could leverage this to execute code in the context of the application's JVM process. Successful exploitation could allow the actor to read sensitive data, modify application state, or disrupt service availability with the privileges of the application process.
Impacted versions: Amazon Redshift JDBC Driver < 2.2.2
Patches This issue has been addressed in Amazon Redshift JDBC Driver version 2.2.2. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes.
References If you have any questions or comments about this advisory, we ask that you contact AWS Security via our vulnerability reporting page or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue.
Acknowledgement We would like to thank Fushuling for collaborating on this issue through the coordinated issue disclosure process.
Other sources
An issue exists in Amazon Redshift JDBC Driver versions prior to 2.2.2. Under certain conditions, the driver could load and execute arbitrary classes when processing JDBC connection URL parameters. An actor who can influence the connection URL could potentially execute code in the application context, provided a suitable class is available on the application's classpath.
To mitigate this issue, users should upgrade to version 2.2.2 or later.
— MITRE
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
maven/com.amazon.redshift:redshift-jdbc42to a version that resolves this vulnerability.Fixed in 2.2.2 - Upgrade
Upgrade
Amazon Redshift JDBC Driverto a version that resolves this vulnerability.Fixed in 2.2.2
Event History
Frequently Asked Questions
What is the severity of CVE-2026-8178?
CVE-2026-8178 is classified as a high-severity vulnerability due to its potential for remote code execution.
How do I fix CVE-2026-8178?
To resolve CVE-2026-8178, upgrade the Amazon Redshift JDBC Driver to version 2.2.2 or later.
What systems are affected by CVE-2026-8178?
CVE-2026-8178 affects all versions of the Amazon Redshift JDBC Driver prior to 2.2.2.
What can attackers do with CVE-2026-8178?
Attackers could exploit CVE-2026-8178 to load and execute arbitrary classes through manipulated JDBC connection URL parameters.
Is there a workaround for CVE-2026-8178?
There are no specified workarounds for CVE-2026-8178, so updating the driver is essential for mitigation.