Remote Code Execution via Unsafe Class Loading in Amazon Redshift JDBC Driver Connection Parameters
Affects Amazon Redshift JDBC Driver versions before 2.3.0 when a suitable class is on the application's classpath and the JDBC connection URL or AWS credentials profile can be influenced. Fixed in 2.3.0.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 2.3.0
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 2.3.0.
- Exploitation?/40Exploitation: unknown (data gap). No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Data gap: Advisories don't say whether default setups are affected
- Reach?/20Reach: unknown (data gap). No tracked technology or package matched
- Severity8.1/10CVSS 8.1
- No patch0/5No signal
What would change the score
- Would score about 70 if added to CISA KEV
- Would score about 65 if CISA's SSVC rates exploitation active
- Would score about 30 if advisories confirm default setups are exposed
CVE-2026-119084 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.1 (high) and affects amazon-redshift-jdbc-driver; fixed in 2.3.0.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 25/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Fix
- Fixed in 2.3.0
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The Amazon Redshift JDBC Driver, a library used by Java applications to connect to Amazon Redshift databases, is affected. An attacker who can control the JDBC connection URL or the AWS credentials profile could potentially run arbitrary code within the application, if a suitable class exists on the application's classpath.
Read the original description
Unsafe reflection in the connection parameter and credentials profile handling of Amazon Redshift JDBC Driver before 2.3.0 might allow an actor who can influence the JDBC connection URL or the AWS credentials profile to execute arbitrary code in the application context, provided a suitable class is available on the application classpath. To remediate this issue, users should upgrade to version 2.3.0 or later.
What to do
Upgrade to a fixed version: 2.3.0.
Workaround: Review how the application builds JDBC connection URLs and AWS credentials profiles, and do not build them from untrusted input, or validate externally supplied values against an allowlist of expected parameters and values.
Timeline
- CVE published
- Record last updated
- First seen by cve.now
Affected versions
- AWS amazon-redshift-jdbc-driver
fixed in 2.3.0
Evidence 3
- Advisory
- Advisory
- Patch
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-119084
Is CVE-2026-119084 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
Connection parameters in the driver's JDBC connection URL or AWS credentials profile can cause the driver to load and run code from classes available on the application's classpath, in the context of the application's JVM process.Source: github.com
Which versions are affected by CVE-2026-119084?
amazon-redshift-jdbc-driver: before 2.3.0.Source: cve.now feed data
Am I affected, and how do I check?
Driver versions before 2.3.0 are affected, and only where a suitable class is on the application's classpath and the JDBC connection URL or credentials profile can be influenced from outside. To check, look at the Amazon Redshift JDBC driver version in the application's dependency configuration, such as the Maven or Gradle file or the driver jar name.Source: github.com
How do I fix CVE-2026-119084?
Upgrade the Amazon Redshift JDBC Driver to version 2.3.0 or later, which contains the fix. Until the upgrade is applied, avoid building JDBC connection URLs and AWS credentials profiles from untrusted input.Source: github.com