Incorrect authorization checks in Amazon Athena engine version 3 query processing
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The vulnerability affects Amazon Athena engine version 3, the query processing engine used by the Amazon Athena service. An authenticated user could have used it to read other AWS accounts' identifiers and SQL query text metadata, though query results and data in Amazon S3 or other data sources were not exposed.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
Incorrect authorization checks in Amazon Athena engine version 3 query processing could have allowed an authenticated user to read AWS account identifiers and SQL statement text query metadata from other AWS accounts. Query results, and data stored in Amazon S3 or other data sources, were not accessible through this issue. AWS remediated the issue on October 7, 2026. No customer action is required.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- AWS Amazon Athena
Version range not reported