Amazon Redshift Vulnerable to Remote Code Execution via Unsafe Class Loading

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

9.2 · CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2026-8178: 0.60% estimated exploitation activity in the next 30 days; percentile 48.57 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary 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. Impact 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 Patches This issue has been addressed in Amazon Redshift…

Published by the source

14 May 2026, 13:09 UTC

Last modified by the source

14 May 2026, 13:09 UTC

Source last checked

26 Oct 2026, 16:45 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-wmmv-vvg5-993q

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-8178

Advisory: Amazon Redshift Vulnerable to Remote Code Execution via Unsafe Class Loading
IDs: CVE-2026-8178, GHSA-wmmv-vvg5-993q
Record: https://patchnext.com/advisories/cve-2026-8178 (revision 1, source checked 26 Oct 2026, 16:45 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.2)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: com.amazon.redshift:redshift-jdbc42 2.2.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven com.amazon.redshift:redshift-jdbc42: affected < 2.2.2; fixed in 2.2.2

## Suggested inspection (read-only)
- Maven com.amazon.redshift:redshift-jdbc42: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on com.amazon.redshift:redshift-jdbc42.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-wmmv-vvg5-993q (GitHub-reviewed advisory GHSA-wmmv-vvg5-993q lists affected ranges: Maven com.amazon.redshift:redshift-jdbc42 >=0 <2.2.2)

Commands are suggestions: review each one before running it.