Quick answers
- Is CVE-2026-119084 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-119084 being exploited in the wild.
- How severe is CVE-2026-119084?
- High severity, with a CVSS score of 8.1, published 3 November 2026.
- Which products and versions are affected?
- Amazon Redshift JDBC Driver prior to 2.3.0.
- Is there a fix for CVE-2026-119084?
- Yes: fixed in 2.3.0. Until then: Do not build JDBC connection URLs or AWS credentials profiles from untrusted input. Validate any externally supplied parameter values against an allowlist of expected parameters and values. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-119084 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-119084?
- Check whether you run Amazon AWS or Amazon Redshift JDBC Driver at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 2.3.0
Do not build JDBC connection URLs or AWS credentials profiles from untrusted input. Validate any externally supplied parameter values against an allowlist of expected parameters and values.
Technical details
The vulnerability exists in JDBC connection parameter and credentials profile processing, where unsafe class loading allows execution of attacker-controlled classes. An attacker with ability to influence connection URLs or credential configuration files can achieve remote code execution within the application context. The issue is fixed in version 2.3.0.
Affected products
- Amazon Redshift JDBC Driver prior to 2.3.0
Timeline
- 2026-11-03: disclosed