Skip to main content
VulnerabilityPublished Updated

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

Affects ansibleSource GCVE Database

0
Compare
Authoritative record:CVE-2024-8775· Medium 5.5

Not known to be exploited · CVSS 5.5 Medium : upgrade to 14.3.0 when convenient.

Data as of 22 Nov 2026, 18:24 UTC

CVSS 3.1 base score
5.5Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (redhat)CVSS 3.15.5
Patch
Available – fixed in 14.3.0
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 14 Sep 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 21 Nov 2026.

What to do

Upgrade ansible to 14.3.0.

Affected software

ProductAffectedFixed in
Homebrewansiblepkg:brew/ansibleOther threatsAffected
  • <14.3.0
Fixed in
  • 14.3.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in Ansible version 14.3.0. Users should upgrade to version 14.3.0 or later to remediate this issue. Additionally, when using tasks that load vaulted variables, the no_log: true parameter should be set to prevent sensitive data from being logged or displayed. Follow the vendor advisory from Red Hat for official patching instructions.

Description

CVE-2024-8775 is a vulnerability in Ansible-core where sensitive information stored in Ansible Vault files can be exposed in plaintext during playbook execution if the no_log: true parameter is not set when loading vaulted variables. This can lead to unintentional disclosure of secrets such as passwords or API keys in logs or output. The issue affects versions prior to 14.3.0 and has been fixed in version 14.3.0.

References

Community reviews

Loading reviews…