{"id":"GHSA-qrph-v96m-w2mv","kind":"vulnerability","aliases":["GHSA-qrph-v96m-w2mv"],"related":[],"title":"CVE-2026-119084 - Remote Code Execution via Unsafe Class Loading in Amazon Redshift JDBC Driver Connection Parameters","description":"CVE-2026-119084 - Remote Code Execution via Unsafe Class Loading in Amazon Redshift JDBC Driver Connection Parameters\n\n### CVE-2026-119084 - Remote Code Execution via Unsafe Class Loading in Amazon Redshift JDBC Driver Connection Parameters\n\nBulletin ID: 2026-168-AWS Scope: AWS Content Type: Important (requires attention) Publication Date: 11/03/2026 13:00 PM PST\n\nDescription:\n\nAmazon 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.\n\nImpacted versions: Amazon Redshift JDBC Driver < 2.3.0\n\nResolution:\n\nThis 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.\n\nWorkarounds:\n\nIf 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.\n\nReferences:\n\n- CVE-2026-119084\n- GHSA-qrph-v96m-w2mv\n\nAcknowledgement:\n\nWe would like to thank 4ra1n, pyn3rd and unam4 for collaborating on this issue through the coordinated vulnerability disclosure process.\n\n Please email aws-security@amazon.com with any security questions or concerns.","summary":"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.","severity":"high","cvss":null,"epss":null,"exploited":false,"exploited_at":null,"products":[],"ecosystems":[],"tags":["aws","java","jdbc","lab-disclosure","package","redshift"],"not_affected_if":["driver-2.3.0-or-later","fixed-connection-strings"],"how_to_check":"- Check the driver version in your build file or dependency tree (for example, the Redshift JDBC artifact in Maven Central) and see whether it is below `2.3.0`\n- Review where your application builds JDBC connection URLs and AWS credentials profiles, and whether any part comes from untrusted input","fix":"- Amazon Redshift JDBC Driver: upgrade to `2.3.0` or later, per the AWS bulletin, and patch any forked or derivative code","status":"open","published_at":null,"first_seen_at":"2026-11-03T21:58:45+00:00","triaged_at":"2026-11-03T21:59:31+00:00","updated_at":"2026-11-03T21:59:31+00:00","category":"package","confidence":0.6,"triage":{"at":"2026-11-03T21:59:31Z","model":"claude-haiku-5-5","output":{"fix":"- Amazon Redshift JDBC Driver: upgrade to `2.3.0` or later, per the AWS bulletin, and patch any forked or derivative code","reach":"unknown","title":"Amazon Redshift JDBC driver: connection parameters can run arbitrary code","impact":"high","summary":"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.","audience":"developers","category":"package","nicknames":[],"who_cares":["redshift","jdbc","java","aws"],"confidence":0.6,"fix_status":"available","needs_auth":"unknown","worst_case":"Arbitrary code runs in the application's context via driver parameters","analyst_note":"","how_to_check":"- Check the driver version in your build file or dependency tree (for example, the Redshift JDBC artifact in Maven Central) and see whether it is below `2.3.0`\n- Review where your application builds JDBC connection URLs and AWS credentials profiles, and whether any part comes from untrusted input","plain_action":"","needs_analyst":false,"not_affected_if":["driver-2.3.0-or-later","fixed-connection-strings"],"who_is_affected":"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.","user_interaction":"unknown","needs_special_setup":"unknown","severity_if_unknown":"high"},"cost_usd":0.000798,"input_tokens":4810,"output_tokens":633,"severity_before":"unknown"},"analyst_status":null,"analyst_note":null,"search":"'-119084':3A,83C,100C,161C,310C '-168':118C '-2026':2A,82C,99C,160C,309C '00':131C '11/03/2026':129C '13':130C '2.3.0':44B,172C,220C,233C '2026':117C '4':142C '4ra1n':322C 'acknowledg':316C 'actor':196C 'address':226C 'allowlist':301C 'amazon':12A,39B,92C,109C,135C,165C,216C,228C,262C 'api':156C 'applic':78B,153C,212C,277C 'arbitrari':49B,182C 'attack':63B 'attent':126C 'avail':259C 'aw':28B,58B,119C,121C,191C,283C 'aws-security@amazon.com':339C 'build':278C,288C 'bulletin':115C 'cannot':271C 'central':267C 'certain':174C 'class':9A,50B,89C,106C,183C 'code':5A,75B,85C,102C,209C,247C 'collabor':327C 'concern':345C 'condit':175C 'connect':16A,54B,68B,96C,113C,148C,187C,201C,280C 'content':122C 'context':80B,213C 'coordin':333C 'could':73B,178C,206C 'credenti':59B,71B,192C,204C,284C 'cve':1A,81C,98C,159C,308C 'databas':147C 'date':128C 'deriv':246C 'descript':134C 'disclosur':33B,335C 'document':264C 'driver':15A,42B,95C,112C,138C,144C,168C,177C,219C,231C,257C 'email':338C 'ensur':242C 'execut':6A,48B,74B,86C,103C,181C,208C 'expect':303C 'extern':296C 'field':61B,194C 'fix':254C 'fork':244C 'ghsa':19A,24A,312C 'ghsa-qrph-v96m-w2mv':18A,23A,311C 'id':116C 'identifi':158C 'immedi':273C 'impact':214C 'import':124C 'incorpor':251C 'influenc':66B,199C 'input':292C 'interfac':155C 'issu':163C,223C,330C 'java':29B 'jdbc':14A,30B,41B,53B,94C,111C,137C,143C,152C,167C,186C,218C,230C,279C 'lab':32B 'lab-disclosur':31B 'latest':239C,256C 'like':319C 'load':10A,46B,90C,107C,179C 'maven':266C 'new':253C 'packag':34B 'paramet':17A,56B,97C,114C,189C,304C 'patch':249C 'pleas':337C 'pm':132C 'potenti':207C 'prior':170C 'process':52B,185C,336C 'profil':60B,72B,193C,205C,285C 'program':154C 'provid':146C 'pst':133C 'public':127C 'pyn3rd':323C 'qrph':20A,25A,313C 'question':343C 'recommend':235C 'redshift':13A,35B,40B,93C,110C,136C,166C,217C,229C,263C 'refer':307C 'remot':4A,84C,101C 'requir':125C 'resolut':221C 'review':274C 'scope':120C 'secur':342C 'standard':151C 'suppli':297C 'thank':321C 'type':123C,141C 'unam4':325C 'unsaf':8A,88C,105C 'untrust':291C 'upgrad':236C,272C 'url':55B,69B,188C,202C,281C 'v96m':21A,26A,314C 'valid':294C 'valu':298C,306C 'version':36B,169C,215C,232C,240C 'via':7A,87C,104C 'vulner':334C 'w2mv':22A,27A,315C 'workaround':268C 'would':318C","nicknames":[],"mitigations":[],"who_affected":"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.","tier":"B","verified":{},"analyst_revisit_at":null,"fix_status":"available","audience":"developers","plain_action":null,"pkeys":[],"ptokens":[],"labels":["aws","high","java","jdbc","labdisclosure","package","redshift"],"campaign_type":null,"first_public_at":null,"kev":null,"cvss_vector":null,"cvss_by":null,"poc_count":0,"sources":[{"source":"lab","external_id":"https://aws.amazon.com/security/security-bulletins/rss/2026-168-aws/#GHSA-qrph-v96m-w2mv","url":"https://aws.amazon.com/security/security-bulletins/rss/2026-168-aws/","severity":null,"published_at":null,"modified_at":null,"first_seen_at":"2026-11-03T21:58:45+00:00","fetched_at":"2026-11-03T21:58:45+00:00","note":"AWS: CVE-2026-119084 - Remote Code Execution via Unsafe Class Loading in Amazon Redshift JDBC Driver Connection Parameters"}],"documents":[{"id":61015,"url":"https://aws.amazon.com/security/security-bulletins/rss/2026-168-aws/","title":"AWS: CVE-2026-119084 - Remote Code Execution via Unsafe Class Loading in Amazon Redshift JDBC Driver Connection Parameters","kind":"advisory","source":"lab","publisher":"research","text":"CVE-2026-119084 - Remote Code Execution via Unsafe Class Loading in Amazon Redshift JDBC Driver Connection Parameters\n\n### CVE-2026-119084 - Remote Code Execution via Unsafe Class Loading in Amazon Redshift JDBC Driver Connection Parameters\n\nBulletin ID: 2026-168-AWS Scope: AWS Content Type: Important (requires attention) Publication Date: 11/03/2026 13:00 PM PST\n\nDescription:\n\nAmazon 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.\n\nImpacted versions: Amazon Redshift JDBC Driver < 2.3.0\n\nResolution:\n\nThis 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.\n\nWorkarounds:\n\nIf 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.\n\nReferences:\n\n- CVE-2026-119084\n- GHSA-qrph-v96m-w2mv\n\nAcknowledgement:\n\nWe would like to thank 4ra1n, pyn3rd and unam4 for collaborating on this issue through the coordinated vulnerability disclosure process.\n\n Please email aws-security@amazon.com with any security questions or concerns.","published_at":null,"relation":"advisory","confidence":null,"note":null}],"notice":"Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai"}