# CVE-2026-127119: Unverified ownership of the default EMR cluster log location in AWS SDK for pandas

> Remote actors can read EMR cluster logs via a pre-created S3 bucket because the SDK uses an unverified default log location.

- **Severity:** Medium 5.9 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Harmful if only installed:** No
- **Needs a specific call:** No
- **Fix available:** No
- **Published:** 12 Nov 2026
- **Updated:** 16 Nov 2026
- **Also known as:** GHSA-3rgm-255m-m9g5

## What is CVE-2026-127119?

CVE-2026-127119 is a medium-severity information disclosure vulnerability in aws-sdk-pandas, published on 12 Nov 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Unverified ownership of the default cluster log location in the EMR module in AWS SDK for pandas (awswrangler) from 1.1.0 before 3.18.0 might allow remote actors to read Amazon EMR cluster logs, including job step output, via a pre-created S3 bucket.

To remediate this issue, users should upgrade to version 3.18.0 or later. Users who can't upgrade immediately should pass an explicit log location, or create the default EMR log bucket in their own account in each region they use.

Weakness: CWE-341 (Predictable from Observable State), CWE-283 (Unverified Ownership)

## Which versions are affected by CVE-2026-127119?

An affected version is exposed as installed. No special setting or call is needed.


## How do I fix CVE-2026-127119?

No fix has been published for CVE-2026-127119 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-127119 being exploited?

There is no known exploitation of CVE-2026-127119 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-127119 and fix it if it is affected.

What it is: CVE-2026-127119 is a medium-severity information disclosure vulnerability in aws-sdk-pandas, published on 12 Nov 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-127119 in the wild and no public exploit code.
Exposure: An affected version is exposed as installed. No special setting or call is needed.

Affected product: aws-sdk-pandas. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-127119/ (Markdown: https://insights.sbomify.com/CVE-2026-127119/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-127119
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-127119
- OSV: https://osv.dev/vulnerability/CVE-2026-127119

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-127119/
Summaries are generated and may contain mistakes; the official description above is the record.
