AWS SDK for pandas 3.16.1 Fixes Athena Result-Bucket Ownership Flaw
Tech GuruQuick Answer
AWS bulletin 2026-153-AWS fixes CVE-2026-118029 in the AWS SDK for pandas Athena module. Upgrade to 3.16.1 or later, identify default query-result buckets, verify ownership and policies, assess prior result exposure or tampering risk, and retain evidence.
Confirm Scope And Apply The Supported Remediation
What to do now: Inventory applications, notebooks and pipelines using awswrangler Athena APIs, exact package versions, accounts and regions, workgroup result settings, default S3 result buckets, bucket owners, data sensitivity, and execution roles. Confirm that the affected module could use its automatically created default result location; do not infer exposure when an explicitly controlled result location or enforced workgroup setting was used. Upgrade AWS SDK for pandas to 3.16.1 or later. While rollout is pending, explicitly set a verified result location or enforce the Athena workgroup result configuration as AWS describes. Confirm lockfiles and deployed package versions, verify S3 bucket ownership, policy and account boundaries, run representative Athena queries, assess historical objects and returned data where warranted, and retain package and configuration evidence.
Last verified: 2026-10-28 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.
Scope And Authority
| Product scope | AWS SDK for pandas (awswrangler) Athena module |
|---|---|
| Advisory | 2026-153-AWS |
| CVE | CVE-2026-118029 |
| Authoritative release date | 2026-10-28 15:30:00 UTC |
| Authority revision date | 2026-10-28 15:40:38 UTC |
| Affected versions | AWS SDK for pandas releases before 3.16.1 when Athena uses an automatically created default S3 query-result location without first verifying bucket ownership. |
| Fixed version | AWS SDK for pandas 3.16.1 or later |
| CVSS base score | Not provided by the authority |
| CVSS severity | Not provided by the authority |
| Exploitation status | AWS does not state that this issue is being maliciously exploited.; no exploitation claim is inferred. |
What Changed
AWS fixed an Athena integration that did not verify ownership of the default query-result bucket, allowing a remote actor who pre-created that bucket to read query results or tamper with returned data.
What To Validate Now
- Inventory. Inventory applications, notebooks and pipelines using awswrangler Athena APIs, exact package versions, accounts and regions, workgroup result settings, default S3 result buckets, bucket owners, data sensitivity, and execution roles.
- Establish applicability. Confirm that the affected module could use its automatically created default result location; do not infer exposure when an explicitly controlled result location or enforced workgroup setting was used.
- Remediate. Upgrade AWS SDK for pandas to 3.16.1 or later. While rollout is pending, explicitly set a verified result location or enforce the Athena workgroup result configuration as AWS describes.
- Validate. Confirm lockfiles and deployed package versions, verify S3 bucket ownership, policy and account boundaries, run representative Athena queries, assess historical objects and returned data where warranted, and retain package and configuration evidence.
- Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.
Operational Cautions
A pre-created bucket could expose results and affect data integrity. Preserve relevant S3, CloudTrail and Athena evidence before cleanup when ownership or query-result anomalies are found.
Evidence To Retain
- Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
- UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
- Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.
Related TechGeeks Resources
Authoritative References
Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.
