AWS credential disclosure via unredacted legacy function
Published Aug 3, 2026 · Updated Aug 3, 2026
Incorrect authorization in DuckDB AWS Extension before commit 7d04119 allows remote authenticated users to disclose AWS credentials. The legacy load_aws_credentials function lets redact_secret=false return the AWS SDK credential chain in plaintext despite the database-wide redaction policy. Exploitation requires SQL execution permission and a reachable credential source, and exposes immediately usable access keys, secret keys, and session tokens.
Summary
What happened
Incorrect authorization in DuckDB AWS Extension before commit 7d04119 allows remote authenticated users to disclose AWS credentials. The legacy load_aws_credentials function lets redact_secret=false return the AWS SDK credential chain in plaintext despite the database-wide redaction policy. Exploitation requires SQL execution permission and a reachable credential source, and exposes immediately usable access keys, secret keys, and session tokens.
The record
- CVE
- CVE-2026-58139
- Published
- Aug 3, 2026
- Updated
- Aug 3, 2026
- Vendor
- DuckDB
- Product
- DuckDB AWS Extension
- Classifications
- CWE-863, T1552
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 3, 2026CVE publishedPublication date reported by the CVE source.
- Aug 3, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <7d04119ee8d3f8836e278f0e8cbf21827ff5338b
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo