Ansible-core: exposure of sensitive information in ansible vault files due to improper logging (CVE-2024-8775)

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

Affected software not mapped in the current feed; confirm the named product and version against your inventory.

Recommended response

Confirm exposure. Identify whether the named product or interface exists in your inventory, then review the linked upstream references for affected versions and vendor guidance.

Evidence timeline and material changes

Published upstream
Sep 14, 2024
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 17, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 17, 2026

Sources and claim methodology

Upstream source description

A flaw was found in Ansible, where sensitive information stored in Ansible Vault files can be exposed in plaintext during the execution of a playbook. This occurs when using tasks such as include_vars to load vaulted variables without setting the no_log: true parameter, resulting in sensitive data being printed in the playbook output or logs. This can lead to the unintentional disclosure of secrets like passwords or API keys, compromising security and potentially allowing unauthorized access or actions.

Quoted source text, attributed separately from HOL analysis.