{"answers":{"affected":"2 open source packages ship an affected version, including com.amazon.redshift:redshift-jdbc42.","exploited":"There is no known exploitation of CVE-2026-8178 in the wild and no public exploit code.","fix":"Upgrade com.amazon.redshift:redshift-jdbc42 to 2.2.2 or later.","what":"CVE-2026-8178 is a critical code injection vulnerability in Amazon Redshift JDBC Driver, published on 8 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-8178 and fix it if it is affected.\n\nWhat it is: CVE-2026-8178 is a critical code injection vulnerability in Amazon Redshift JDBC Driver, published on 8 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-8178 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- com.amazon.redshift:redshift-jdbc42 (Maven): affected all versions; fixed in 2.2.2\n- com.amazon.redshift:redshift-jdbc42 (Maven): affected all versions; fixed in 2.2.2\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-8178/ (Markdown: https://insights.sbomify.com/CVE-2026-8178/index.md)","id":"CVE-2026-8178","markdown":"https://insights.sbomify.com/CVE-2026-8178/index.md","name":"CVE-2026-8178","record":{"aliases":["GHSA-wmmv-vvg5-993q"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Amazon Redshift JDBC Driver","requires_auth":"none","summary":"Attackers can execute arbitrary code by manipulating JDBC connection URLs to load unsafe classes in applications using the Amazon Redshift JDBC Driver.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"AMZN","cpe":[],"cvss":{"score":9.2,"severity":"critical","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-470","name":"Use of Externally-Controlled Input to Select Classes or Code"}],"description":"An issue exists in Amazon Redshift JDBC Driver versions prior to 2.2.2. Under certain conditions, the driver could load and execute arbitrary classes when processing JDBC connection URL parameters. An actor who can influence the connection URL could potentially execute code in the application context, provided a suitable class is available on the application's classpath.\n\nTo mitigate this issue, users should upgrade to version 2.2.2 or later.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Remote Code Execution via Unsafe Class Loading in Amazon Redshift JDBC Driver","id":"CVE-2026-8178","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"code_injection","year":"2026"},"n_packages":2,"n_references":3,"next":{"headline":"Multiple vulnerabilities in Aspera applications.","id":"CVE-2026-8179"},"packages":[{"ecosystem":"Maven","fixed":["2.2.2"],"introduced":["0"],"last_affected":[],"package":"com.amazon.redshift:redshift-jdbc42","purl":null,"source":"GHSA-wmmv-vvg5-993q"},{"ecosystem":"Maven","fixed":["2.2.2"],"introduced":["0"],"last_affected":[],"package":"com.amazon.redshift:redshift-jdbc42","purl":"pkg:maven/com.amazon.redshift/redshift-jdbc42","source":"GHSA-wmmv-vvg5-993q"}],"prev":{"headline":"Memory corruption in XML::LibXML","id":"CVE-2026-8177"},"products":["Amazon Redshift JDBC Driver"],"published":"2026-05-08","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-10-20","vendors":["Amazon"]},"summary":"Attackers can execute arbitrary code by manipulating JDBC connection URLs to load unsafe classes in applications using the Amazon Redshift JDBC Driver.","url":"https://insights.sbomify.com/CVE-2026-8178/"}