Amazon Athena up to 2026 Query Processing improper authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.0 | $0-$5k | 4.55+ |
Summary
A vulnerability has been found in Amazon Athena up to 2026 and classified as problematic. Affected by this vulnerability is an unknown functionality of the component Query Processing. Performing a manipulation results in improper authorization. This vulnerability is reported as CVE-2026-115416. The attack is possible to be carried out remotely. No exploit exists. This product is a managed service, so users are unable to manage vulnerability countermeasures on their own.
Details
A vulnerability was found in Amazon Athena up to 2026. It has been classified as problematic. This affects an unknown part of the component Query Processing. The manipulation with an unknown input leads to a improper authorization vulnerability. CWE is classifying the issue as CWE-285. The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action. This is going to have an impact on confidentiality. The summary by CVE is:
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.
The advisory is shared at aws.amazon.com. This vulnerability is uniquely identified as CVE-2026-115416 since 10/22/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 10/22/2026). MITRE ATT&CK project uses the attack technique T1548.002 for this issue.
This product is available as a managed service. Users are not able to maintain vulnerability countermeasures themselves.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
License
Managed Service
- yes
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 6.0VulDB Meta Temp Score: 6.0
VulDB Base Score: 4.3
VulDB Temp Score: 4.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 7.7
CNA Vector (AMZN): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Improper authorizationCWE: CWE-285 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Status: 🔍0-Day Time: 🔒
Timeline
10/22/2026 Advisory disclosed10/22/2026 CVE reserved
10/22/2026 VulDB entry created
10/22/2026 VulDB entry last update
Sources
Advisory: aws.amazon.comStatus: Not defined
CVE: CVE-2026-115416 (🔒)
GCVE (CVE): GCVE-0-2026-115416
GCVE (VulDB): GCVE-100-425337
Entry
Created: 10/22/2026 19:09Changes: 10/22/2026 19:09 (74)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.