DuckDB AWS extension load_aws_credentials redact_secret missing encryption

Summaryinfo

A vulnerability has been found in DuckDB and classified as problematic. Affected by this issue is the function load_aws_credentials of the component AWS extension. The manipulation of the argument redact_secret leads to missing encryption. This vulnerability is documented as CVE-2026-58139. The attack can be initiated remotely. There is not any exploit available.

Detailsinfo

A vulnerability, which was classified as problematic, has been found in DuckDB (the affected version unknown). This issue affects the function load_aws_credentials of the component AWS extension. The manipulation of the argument redact_secret with an unknown input leads to a missing encryption vulnerability. Using CWE to declare the problem leads to CWE-311. The product does not encrypt sensitive or critical information before storage or transmission. Impacted is confidentiality. The summary by CVE is:

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.

The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-58139 since 06/29/2026. The exploitation is known to be difficult. The attack may be initiated remotely. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1600 for this issue.

Applying the patch 7d04119ee8d3f8836e278f0e8cbf21827ff5338b is able to eliminate this problem.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

• DuckDB

CPE 2.3info

• 🔒

CPE 2.2info

• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion