# CVE-2024-8775: Ansible-core: exposure of sensitive information in ansible vault files due to improper logging > Attackers can view sensitive secrets in logs when Ansible Vault variables are loaded without no_log enabled, exposing passwords and API keys. - **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 14 Sep 2024 - **Updated:** 17 Sep 2026 - **Also known as:** AZL-53163, AZL-53180, DEBIAN-CVE-2024-8775, GHSA-jpxc-vmjf-9fcj, PYSEC-2026-1124, SUSE-RU-2025:0791-1, UBUNTU-CVE-2024-8775 ## What is CVE-2024-8775? CVE-2024-8775 is a medium-severity vulnerability in Red Hat Ansible Automation Platform Execution Environments, published on 14 Sep 2024. It can only be exploited from the same machine or local network, with no action from the victim. ### Official 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. Weakness: CWE-532 (Insertion of Sensitive Information into Log File) ## Which versions are affected by CVE-2024-8775? 5 open source packages ship an affected version, including ansible-core. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `ansible-core` | PyPI | All versions | 2.16.13, 2.17.6 | | `ansible-core` | PyPI | All versions | 2.16.13 | | `ansible-core` | PyPI | All versions | 2.16.13 | | `ansible-core` | PyPI | From 2.17.0b1 | 2.17.6 | | `ansible-core` | PyPI | From 2.17.0b1 | 2.17.6 | | `ansible` | SUSE:Manager Client Tools 15 | All versions | 2.9.27-150000.1.20.1 | | `spacewalk-client-tools` | SUSE:Manager Client Tools 15 | All versions | 4.3.22-150000.3.100.1 | | `uyuni-proxy-systemd-services` | SUSE:Manager Client Tools 15 | All versions | 4.3.15-150000.1.30.1 | | `uyuni-proxy-systemd-services` | SUSE:Manager Client Tools for SLE Micro 5 | All versions | 4.3.15-150000.1.30.1 | | `ansible` | SUSE:Manager Proxy Module 4.3 | All versions | 2.9.27-150000.1.20.1 | | `uyuni-proxy-systemd-services` | SUSE:Manager Proxy Module 4.3 | All versions | 4.3.15-150000.1.30.1 | | `ansible` | openSUSE:Leap 15.6 | All versions | 2.9.27-150000.1.20.1 | ## How do I fix CVE-2024-8775? Upgrade ansible-core to a fixed version for your release line: 2.16.13 or 2.17.6. ## Is CVE-2024-8775 being exploited? There is no known exploitation of CVE-2024-8775 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-8775 and fix it if it is affected. What it is: CVE-2024-8775 is a medium-severity vulnerability in Red Hat Ansible Automation Platform Execution Environments, published on 14 Sep 2024. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2024-8775 in the wild and no public exploit code. Affected packages and fixed versions: - ansible-core (PyPI): affected all versions; fixed in 2.16.13, 2.17.6 - ansible-core (PyPI): affected all versions; fixed in 2.16.13 - ansible-core (PyPI): affected all versions; fixed in 2.16.13 - ansible-core (PyPI): affected from 2.17.0b1; fixed in 2.17.6 - ansible-core (PyPI): affected from 2.17.0b1; fixed in 2.17.6 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-2024-8775/ (Markdown: https://insights.sbomify.com/CVE-2024-8775/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-8775 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-8775 - OSV: https://osv.dev/vulnerability/CVE-2024-8775 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-8775/ Summaries are generated and may contain mistakes; the official description above is the record.