CVE-2026-8178: Remote Code Execution via Unsafe Class Loading in Amazon Redshift JDBC Driver

Published May 8, 2026
·
Updated

### 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](https://github.com/aws/amazon-redshift-jdbc-driver/releases/tag/v2.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](https://aws.amazon.com/security/vulnerability-reporting) or directly via email to [aws-security@amazon.com](mailto:aws-security@amazon.com). Please do not create a public GitHub issue. ### Acknowledgement We would like to thank [Fushuling](https://github.com/Fushuling) for collaborating on this issue through the coordinated issue disclosure process.

Affected Software

2 affected componentsFixes available
Amazon Amazon Redshift JDBC Driver<2.2.2
maven/com.amazon.redshift:redshift-jdbc42<2.2.2
2.2.2

Event History

May 8, 2026
CVE Published
via MITRE·06:36 PM
Data Sourced
via MITRE·06:36 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·07:16 PM
DescriptionSeverityWeakness
May 14, 2026
Advisory Published
via GitHub·01:09 PM
Data Sourced
via GitHub·01:09 PM
DescriptionSeverityWeaknessAffected Software
Oct 13, 58358
Event
via FIRST·07:48 PM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

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.

2

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.

3

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.

4

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.

5

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.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203