CVE-2026-35559 Amazon CVE debrief

Who should care

Users of Amazon Athena ODBC driver versions before 2.1.0.0 should upgrade to prevent potential driver crashes. This includes operators, platform administrators, vulnerability management teams, and security teams who need to review and update affected systems and applications. The vulnerability has a CVSS score of 7.1 and is classified as HIGH severity, indicating high priority for remediation.

Technical summary

The Amazon Athena ODBC driver before version 2.1.0.0 has an out-of-bounds write vulnerability in its query processing components. This might allow a threat actor to crash the driver by using specially crafted data during query operations. The vulnerability has a CVSS score of 7.1 and is classified as HIGH severity. Users of Amazon Athena ODBC driver versions before 2.1.0.0 should upgrade to version 2.1.0.0 or later to prevent potential driver crashes.

Defensive priority

High priority should be given to upgrading the Amazon Athena ODBC driver to version 2.1.0.0 or later. This is due to the HIGH severity of the vulnerability and the potential for a threat actor to crash the driver using specially crafted data during query operations.

Recommended defensive actions

• Upgrade to Amazon Athena ODBC driver version 2.1.0.0 or later
• Review and update affected systems and applications
• Monitor for potential exploitation attempts
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

Evidence is based on official CVE and NVD records, as well as vendor advisories and release notes. The Amazon Athena ODBC driver before version 2.1.0.0 has an out-of-bounds write vulnerability in its query processing components. This might allow a threat actor to crash the driver by using specially crafted data during query operations. Evidence limits suggest that affected deployments should be verified for potential exposure. Defenders should review official advisories and CVE records for affected scope, severity, and vendor guidance.

Official resources