CVE-2026-8178

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.

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 [email protected]. 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.

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

CVE-2026-8178 has a CVSS score of 8.1 (Critical). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.2.2); upgrading removes the vulnerable code path.

Kodem intelligence

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.

1. What is CVE-2026-8178? CVE-2026-8178 is a critical-severity security vulnerability in com.amazon.redshift:redshift-jdbc42 (maven), affecting versions < 2.2.2. It is fixed in 2.2.2.
2. How severe is CVE-2026-8178? CVE-2026-8178 has a CVSS score of 8.1 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of com.amazon.redshift:redshift-jdbc42 are affected by CVE-2026-8178? com.amazon.redshift:redshift-jdbc42 (maven) versions < 2.2.2 is affected.
4. Is there a fix for CVE-2026-8178? Yes. CVE-2026-8178 is fixed in 2.2.2. Upgrade to this version or later.
5. Is CVE-2026-8178 exploitable, and should I be worried? Whether CVE-2026-8178 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-8178 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-8178? Upgrade com.amazon.redshift:redshift-jdbc42 to 2.2.2 or later.