# CVE-2026-127119: AWS SDK for pandas EMR unverified bucket ownership

Source: https://junglewise.ai/threats/cve-2026-127119-unverified-ownership-of-the-default-emr-cluster-log-location-in  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-11-12. Updated: 2026-11-12  
License: CC BY 4.0 with a link back

CVE-2026-127119 · Severity: high · CVSS 5.3 · Published 2026-11-12

AWS SDK for pandas (awswrangler) is a library for data processing on Amazon's EMR analytics platform. When creating an EMR cluster without specifying a log location, the library writes logs to a predictable S3 bucket without checking if the account actually owns that bucket. An attacker could pre-register the bucket name and intercept sensitive job logs and output data.

Technologies: [Amazon AWS](https://junglewise.ai/threats/technologies/aws). Vendors: [Amazon](https://junglewise.ai/threats/vendors/amazon), [Amazon Web Services](https://junglewise.ai/threats/vendors/amazon-web-services).

## Quick answers

**Is CVE-2026-127119 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-127119 being exploited in the wild.

**How severe is CVE-2026-127119?** High severity, with a CVSS score of 5.3, published 12 November 2026.

**Which products and versions are affected?** Amazon Web Services SDK for pandas 1.1.0 to before 3.18.0.

**Is there a fix for CVE-2026-127119?** Yes: fixed in 3.18.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-127119 attacked?** It is attacked over the network, in a software library.

**Am I affected by CVE-2026-127119?** Check whether you run Amazon AWS or Amazon Web Services SDK for pandas at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- Fixed in 3.18.0

## Technical details

The vulnerability exists in the EMR module of awswrangler versions 1.1.0 to 3.17.x, which uses a deterministic default S3 bucket name for cluster logs without ownership verification. An attacker can exploit this by creating an S3 bucket with the predictable name in advance, allowing read access to logs from any user's EMR cluster that does not specify an explicit log location. The issue requires network access to AWS S3 and knowledge of the predictable bucket naming scheme.

## Affected products

- Amazon Web Services SDK for pandas 1.1.0 to before 3.18.0

## Timeline

- 2026-11-12: disclosed

## References

- [https://aws.amazon.com/security/security-bulletins/rss/2026-181-aws/](https://aws.amazon.com/security/security-bulletins/rss/2026-181-aws/)

## Related threats

- [An untrusted search path issue in Aurora PostgreSQL dialect detection in the AWS Advanced Go Wrapper from release 2026-04-06 (awssql/v2.0.0)](https://junglewise.ai/threats/cve-2026-126793-privilege-escalation-in-aurora-postgresql-dialect-detection-in)
- [Amazon mcp-gateway-registry server-side request forgery in registration API](https://junglewise.ai/threats/cve-2026-125926-server-side-request-forgery-in-the-server-registration-and)
- [Amazon mcp-gateway-registry authorization bypass in management API](https://junglewise.ai/threats/cve-2026-100307-missing-authorization-on-the-external-management-api-in-mcp)
- [AWS Kiro CLI incorrect default permissions on session files](https://junglewise.ai/threats/cve-2026-124848-incorrect-default-permissions-on-session-transcripts-and-prompt)
- [OpenJD Sessions for Python untrusted search path in process launcher](https://junglewise.ai/threats/cve-2026-126087-untrusted-search-path-in-openjd-sessions-for-python-and-the-aws)