# CVE-2026-58139: DuckDB AWS Extension Security Policy Bypass via load_aws_credentials Procedure

> Attackers with SQL access can bypass redaction policies to extract plaintext AWS credentials via the load_aws_credentials function in the DuckDB AWS extension.

- **Severity:** Medium 6.0 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Aug 2026
- **Updated:** 14 Aug 2026
- **Also known as:** GHSA-g2r8-97m7-62w9

## What is CVE-2026-58139?

CVE-2026-58139 is a medium-severity vulnerability in duckdb-aws, published on 3 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The DuckDB AWS extension for DuckDB contains a security policy bypass vulnerability that allows any database user with SQL execution permissions to extract plaintext AWS credentials by calling the load_aws_credentials function with the redact_secret parameter set to false, circumventing the database-wide allow_unredacted_secrets=false policy. Attackers can invoke this single function to retrieve the underlying AWS credential chain including access_key_id, secret_access_key, session_token, and region in plaintext, which are immediately valid against AWS APIs and particularly impactful in managed environments where pg_duckdb is preloaded and an AWS credential chain such as IMDSv2, IRSA, ECS task role, or EC2 instance role is reachable.

Weakness: CWE-863 (Incorrect Authorization)

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


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

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

## Is CVE-2026-58139 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-58139 is a medium-severity vulnerability in duckdb-aws, published on 3 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-58139 in the wild and no public exploit code.

Affected product: duckdb-aws. 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-58139/ (Markdown: https://insights.sbomify.com/CVE-2026-58139/index.md)
```

## Sources

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

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