How severe is CVE-2024-11079?

CVE-2024-11079 has a CVSS score of 5.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2024-11079?

CVE-2024-11079 affects the following packages: ansible-core (PyPI), ansible-core (PyPI), ansible-core (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2024-11079?

Update ansible-core to 2.18.1rc1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-11079 is resolved across your whole dependency graph.

How do I detect CVE-2024-11079 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ansible-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2024-11079 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2024-11079 actively exploited in the wild?

No public exploit code has been indexed for CVE-2024-11079 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2024-11079?

CVE-2024-11079 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 45th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2024-11079?

CVE-2024-11079 is classified as Improper Input Validation (CWE-20). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2024-11079 published, and has it been updated?

CVE-2024-11079 was published on November 11, 2024 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍

🐍 PyPI

Not in CISA KEV

MEDIUM severity

CVE-2024-11079 — ansible-core

MEDIUMFix: ansible/ansible#84299

CVE-2024-11079 is a medium-severity (CVSS 5.5) Improper Input Validation vulnerability in ansible-core. A fix is available for ansible-core — see the affected versions and patch details below.

Ansible-core: unsafe tagging bypass via hostvars object in ansible-core

Also known asGHSA-99w6-3xph-cx78PYSEC-2026-1123

Published

Nov 11, 2024

Updated

Oct 28, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Exploitation data as of Oct 30, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2024-11079.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk+0.03%

Lower risk than most CVEs45th percentile — riskier than 45% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

3 pkgs affected

🐍ansible-core🐍ansible-core🐍ansible-core

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

A flaw was found in Ansible-Core. This vulnerability allows attackers to bypass unsafe content protections using the hostvars object to reference and execute templated content. This issue can lead to arbitrary code execution if remote data or module outputs are improperly templated within playbooks.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`ansible-core`	≥ 2.18.0b1&&< 2.18.1rc1	2.18.1rc1`pip install --upgrade 'ansible-core==2.18.1rc1'`
🐍PyPI	`ansible-core`	≥ 2.17.0b1&&< 2.17.7rc1	2.17.7rc1`pip install --upgrade 'ansible-core==2.17.7rc1'`
🐍PyPI	`ansible-core`	all versions	2.16.14rc1`pip install --upgrade 'ansible-core==2.16.14rc1'`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ansible-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update ansible-core to 2.18.1rc1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-11079 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

Workaround published by Red Hat

To mitigate this vulnerability, avoid using the hostvars object to reference content marked as !unsafe. Ensure that all remote data from modules or lookups is properly sanitized and validated before use in playbooks. Additionally, restrict access to inventory files and Ansible playbooks to trusted users to minimize exploitation risks.

Source: Red Hat security advisory for CVE-2024-11079 (CC BY 4.0)

Product	Fixed in	Advisory
Ansible Automation Platform Execution Environments	`ansible-automation-platform/ansible-builder-rhel8:1.2.0-93`	RHSA-2024:10770
Red Hat Ansible Automation Platform 2.5 for RHEL 8	`ansible-core-1:2.16.14-1.el8ap`	RHSA-2024:11145

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2024-11079 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works