Live › vulnerability › GHSA-qrph-v96m-w2mv
Versions of the Amazon Redshift JDBC driver before 2.3.0 can load and execute arbitrary classes when processing JDBC connection URL parameters or AWS credentials profile fields. An attacker who can influence the connection URL or credentials profile could execute code in the application's context.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-11-03 21:58 UTC. All times on this page are UTC.
Applications that use the Amazon Redshift JDBC driver before 2.3.0 are exposed, and the risk is highest where the connection URL or AWS credentials profile fields are built from or influenced by untrusted input. Teams whose connection strings are fixed in configuration and never derived from outside data face a lower risk, but the AWS bulletin still recommends upgrading.
No product ranges from the sources yet.
2.3.02.3.0 or later, per the AWS bulletin, and patch any forked or derivative codeEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
CVE-2026-119084 - Remote Code Execution via Unsafe Class Loading in Amazon Redshift JDBC Driver Connection Parameters
Bulletin ID: 2026-168-AWS Scope: AWS Content Type: Important (requires attention) Publication Date: 11/03/2026 13:00 PM PST
Description:
Amazon Redshift JDBC Driver is a Type 4 JDBC driver that provides database connectivity through the standard JDBC application program interfaces (APIs). We identified CVE-2026-119084, an issue in Amazon Redshift JDBC Driver versions prior to 2.3.0. Under certain conditions, the driver could load and execute arbitrary classes when processing JDBC connection URL parameters or AWS credentials profile fields. An actor who can influence the connection URL or credentials profile could potentially execute code in the application context.
Impacted versions: Amazon Redshift JDBC Driver < 2.3.0
Resolution:
This issue has been addressed in Amazon Redshift JDBC Driver version 2.3.0. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. The latest driver is available from the Amazon Redshift documentation and Maven Central.
Workarounds:
If you cannot upgrade immediately, review how your application builds JDBC connection URLs and AWS credentials profiles. Do not build them from untrusted input, or validate any externally supplied values against an allowlist of expected parameters and values.
References:
Acknowledgement:
We would like to thank 4ra1n, pyn3rd and unam4 for collaborating on this issue through the coordinated vulnerability disclosure process.
Please email [email protected] with any security questions or concerns.
This page as .md · .json · in your agent: get_signal("GHSA-qrph-v96m-w2mv")