AWS SDK for pandas Update Verifies EMR Log Bucket Ownership
Tech GuruQuick Answer
Update to 3.18.0, confirm ownership of EMR log buckets and provide s3:ListBucket for the ownership check. Use an explicit bucket you own while upgrading.
Confirm Scope And Apply The Supported Remediation
What to do now: Inventory awswrangler callers, regions, log locations, bucket ownership and EMR role permissions. Match the installed library and stated access/configuration prerequisites; AWS service use alone does not establish exposure. awswrangler 3.18.0 or later. Apply the corresponding fix to forks and derivative deployments. Verify ownership and authorized log delivery with a controlled cluster. Review historical destinations and log contents, preserving bucket, IAM and job evidence.
Last verified: 2026-11-13 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.
Scope And Authority
| Product scope | AWS SDK for pandas (awswrangler) EMR cluster creation |
|---|---|
| Advisory | GHSA-3rgm-255m-m9g5 / 2026-181-AWS |
| CVE | CVE-2026-127119 |
| Authoritative release date | 2026-11-12 — 2026-11-12 20:04:59 UTC (AWS repository advisory). |
| Authority revision date | No separate revision date is provided by the authority. |
| Affected versions | awswrangler >=1.1.0 and <3.18.0 when no explicit log location is supplied, the caller does not already own the default bucket, and EMR roles permit writes to other accounts. |
| Fixed version | awswrangler 3.18.0 or later |
| CVSS base score | 5.3 (CVSS v3.1 base score) |
| CVSS severity | Medium |
| Exploitation status | AWS does not confirm exploitation in the wild in the cited advisories.; no exploitation claim is inferred. |
What Changed
The default EMR log bucket can be claimed by another account, exposing cluster logs, step output, scripts and configuration. AWS does not attribute modification of job data or loss of cluster availability to this issue.
What To Validate Now
- Inventory. Inventory awswrangler callers, regions, log locations, bucket ownership and EMR role permissions.
- Establish applicability. Match the installed library and stated access/configuration prerequisites; AWS service use alone does not establish exposure.
- Remediate. awswrangler 3.18.0 or later. Apply the corresponding fix to forks and derivative deployments.
- Validate. Verify ownership and authorized log delivery with a controlled cluster. Review historical destinations and log contents, preserving bucket, IAM and job 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
If the predictable bucket name belongs to another account, treat it as untrusted and choose an explicit owned location. The new ownership check may fail without s3:ListBucket.
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.
