CVE-2024-8775VulnerabilityPublished 14 Sep 2024Updated 17 Sep 2026

CVE-2024-8775: Red Hat Ansible Automation Platform Execution Environments · Sensitive Data in Logs

Affects Red Hat Ansible Automation Platform Execution EnvironmentsSource CVE Database V5

Not known to be exploited · CVSS 5.5 Medium.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 3.1 base score

5.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 19% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Attack Vector: Local
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 14 Sep 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Red HatAnsible Automation Platform Execution Environments	Affected–	Fixed in–
Red HatAnsible Automation Platform Execution Environments	Affected–	Fixed in–
Red HatAnsible Automation Platform Execution Environments	Affected–	Fixed in–
Red HatAnsible Automation Platform Execution Environments	Affected–	Fixed in–
Red HatAnsible Automation Platform Execution Environments	Affected–	Fixed in–
Red HatDiscovery 1 for RHEL 9	Affected–	Fixed in–
Red HatRed Hat Ansible Automation Platform 2.4 for RHEL 8	Affected–	Fixed in–
Red HatRed Hat Ansible Automation Platform 2.4 for RHEL 9	Affected–	Fixed in–
Red HatRed Hat Ansible Automation Platform 2.5 for RHEL 8	Affected–	Fixed in–
Red HatRed Hat Ansible Automation Platform 2.5 for RHEL 9	Affected–	Fixed in–
Red HatRed Hat Enterprise Linux 10	Affected–	Fixed in–
Red HatRed Hat Enterprise Linux 8	Affected–	Fixed in–
Red HatRed Hat Enterprise Linux 9	Affected–	Fixed in–
Red HatRed Hat Enterprise Linux AI (RHEL AI)	Affected–	Fixed in–
GitHubansible-core`pkg:github/ansible-core`Other threats	Affected >=1.0.0 <=2.17.4	Fixed in–
GitHubansible/ansible`pkg:github/ansible/ansible`Other threats	Affected =1.0.0	Fixed in–

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

AI-suggested

To mitigate CVE-2024-8775, organizations should immediately review all Ansible playbooks that load vaulted variables using include_vars or similar tasks. Ensure that the no_log: true parameter is set wherever sensitive data is handled to prevent logging of plaintext secrets. Audit existing logs for accidental exposure of secrets and rotate any credentials found in logs. Upgrade Ansible to a version where this vulnerability is patched once available. Implement strict access controls on systems running Ansible playbooks and on log storage locations to limit exposure. Use centralized secret management solutions integrated with Ansible that minimize the need to decrypt secrets in playbooks. Educate DevOps and automation teams on secure playbook practices, emphasizing the risks of logging sensitive information. Regularly scan playbooks and automation pipelines for insecure logging configurations. Consider employing monitoring tools to detect anomalous access to logs or unusual playbook executions.

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.

Impact

The primary impact of CVE-2024-8775 is the potential exposure of sensitive secrets such as passwords, API keys, and tokens stored in Ansible Vault files. If these secrets are logged in plaintext, unauthorized users with access to logs can retrieve them, leading to credential compromise. This can facilitate unauthorized access to critical systems, cloud environments, or services automated by Ansible, potentially enabling lateral movement or data exfiltration. While the vulnerability does not directly affect system integrity or availability, the confidentiality breach can have cascading effects on organizational security posture. Organizations with extensive use of Ansible for automation, especially in regulated industries or those managing sensitive infrastructure, face increased risk of data leakage and compliance violations. The requirement for local access limits remote exploitation but insider threats or compromised accounts could leverage this flaw. The absence of known exploits suggests the vulnerability is not yet actively weaponized but should be addressed proactively.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 27 Feb 2026, 16:19 UTC

Technical details

References

Community reviews

Related threats