Vault secret disclosure via unredacted task output
Published Sep 14, 2024 · Updated Nov 6, 2025
Information disclosure in Ansible Core before 2.16.13 and 2.17.0b1 through 2.17.5 allows local users to read Vault secrets from logs. Tasks such as include_vars load vaulted variables without automatically suppressing their plaintext values from playbook output and logging callbacks. Exploitation requires playbook execution without no_log enabled and access to the resulting output or logs, exposing passwords, API keys, or other stored secrets.
Summary
What happened
Information disclosure in Ansible Core before 2.16.13 and 2.17.0b1 through 2.17.5 allows local users to read Vault secrets from logs. Tasks such as include_vars load vaulted variables without automatically suppressing their plaintext values from playbook output and logging callbacks. Exploitation requires playbook execution without no_log enabled and access to the resulting output or logs, exposing passwords, API keys, or other stored secrets.
The record
- CVE
- CVE-2024-8775
- Published
- Sep 14, 2024
- Updated
- Nov 6, 2025
- Vendor
- Red Hat
- Product
- Red Hat Enterprise Linux 10
- Classifications
- CWE-532, T1552.001
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 14, 2024CVE publishedPublication date reported by the CVE source.
- Nov 6, 2025Record 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?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
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.
Weakness, pattern, technique
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