# CVE-2026-118029: Unverified ownership of the default Athena query result location in AWS SDK for pandas


- **Severity:** Medium 5.9 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 28 Oct 2026
- **Updated:** 28 Oct 2026

## What is CVE-2026-118029?

CVE-2026-118029 is a medium-severity vulnerability in aws-sdk-pandas, published on 28 Oct 2026. 

### Official description

Unverified ownership of the default query result location in the Athena module in AWS SDK for pandas (awswrangler) before 3.16.1 might allow remote actors to read Athena query results and tamper with result sets returned to the caller via a pre-created S3 bucket. 

To remediate this issue, users should upgrade to version 3.16.1 or later. Users should also verify that the default Athena result bucket in each account and region is owned by their own account, and set an explicit result location or enforce a workgroup result configuration.

Weakness: CWE-283 (Unverified Ownership)

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


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

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

## Is CVE-2026-118029 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-118029 is a medium-severity vulnerability in aws-sdk-pandas, published on 28 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-118029 in the wild and no public exploit code.

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-118029/ (Markdown: https://insights.sbomify.com/CVE-2026-118029/index.md)
```

## Sources

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

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