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