How severe is GHSA-jc69-hjw2-fm86?

GHSA-jc69-hjw2-fm86 has a CVSS score of 7.1/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-jc69-hjw2-fm86?

GHSA-jc69-hjw2-fm86 affects the following packages: com.amazon.redshift:redshift-jdbc42 (Maven). Ecosystems affected: Maven.

How do I fix GHSA-jc69-hjw2-fm86?

Update com.amazon.redshift:redshift-jdbc42 to 2.1.0.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jc69-hjw2-fm86 is resolved across your whole dependency graph.

How do I detect GHSA-jc69-hjw2-fm86 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.amazon.redshift:redshift-jdbc42, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-jc69-hjw2-fm86 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-jc69-hjw2-fm86 actively exploited in the wild?

Yes. There are 2 known exploit references for GHSA-jc69-hjw2-fm86, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for GHSA-jc69-hjw2-fm86?

GHSA-jc69-hjw2-fm86 has an EPSS (Exploit Prediction Scoring System) score of 1.9%, placing it in the 80th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-jc69-hjw2-fm86?

GHSA-jc69-hjw2-fm86 is classified as CWE-704 (CWE-704). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-jc69-hjw2-fm86 published, and has it been updated?

GHSA-jc69-hjw2-fm86 was published on October 12, 2022 and was last updated on July 8, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

HIGH severity

com.amazon.redshift:redshift-jdbc42 vulnerable to remote command executionGHSA-jc69-hjw2-fm86

HIGHFix: aws/amazon-redshift-jdbc-driver@40b143b

GHSA-jc69-hjw2-fm86 is a high-severity (CVSS 7.1) CWE-704 vulnerability in com.amazon.redshift:redshift-jdbc42. 2 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for com.amazon.redshift:redshift-jdbc42 — see the affected versions and patch details below.

Also known asCVE-2022-41828

Published

Oct 12, 2022

Updated

Jul 8, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

2 known

Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-jc69-hjw2-fm86.

EPSS Exploitation Probability

via FIRST.org ↗

1.9%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs80th percentile — riskier than 80% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

☕com.amazon.redshift:redshift-jdbc42

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Impact

A potential remote command execution issue exists within redshift-jdbc42 versions 2.1.0.7 and below. When plugins are used with the driver, it instantiates plugin instances based on Java class names provided via the sslhostnameverifier, socketFactory, sslfactory, and sslpasswordcallback connection properties. In affected versions, the driver does not verify if a plugin class implements the expected interface before instantiatiaton. This can lead to loading of arbitrary Java classes, which a knowledgeable attacker with control over the JDBC URL can use to achieve remote code execution.

Patches

This issue is patched within redshift-jdbc-42 2.1.0.8 and above.

Workarounds

We advise customers using plugins to upgrade to redshift-jdbc42 version 2.1.0.8 or above. There are no known workarounds for this issue.

For more information

If you have any questions or comments about this advisory, please contact AWS Security at [email protected].

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.amazon.redshift:redshift-jdbc42`	all versions	2.1.0.8`com.amazon.redshift:redshift-jdbc42:2.1.0.8`

Affected Products

1 product · 1 configurations

Application

amazon web services redshift java database connectivity driveramazon

< 2.1.0.8

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

In Amazon AWS Redshift JDBC Driver (aka amazon-redshift-jdbc-driver or r…

github.comGithubDec 2022

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.amazon.redshift:redshift-jdbc42, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.amazon.redshift:redshift-jdbc42 to 2.1.0.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jc69-hjw2-fm86 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### Impact A potential remote command execution issue exists within `redshift-jdbc42` versions 2.1.0.7 and below. When plugins are used with the driver, it instantiates plugin instances based on Java class names provided via the `sslhostnameverifier`, `socketFactory`, `sslfactory`, and `sslpasswordcallback` connection properties. In affected versions, the driver does not verify if a plugin class implements the expected interface before instantiatiaton. This can lead to loading of arbitrary Java classes, which a knowledgeable attacker with control over the JDBC URL can use to achieve remote co