Skip to main content
CVE-2025-49520VulnerabilityPublished Updated

CVE-2025-49520: Red Hat Ansible Automation Platform 2.5 for RHEL 8 · Argument Injection

Affects Red Hat Ansible Automation Platform 2.5 for RHEL 8Source CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 48% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 Jun 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: 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 2026-10-25.

What to do

AI-suggested

To mitigate CVE-2025-49520, organizations should immediately apply any patches or updates released by Red Hat for Ansible Automation Platform 2.5. If patches are not yet available, restrict access to the EDA component to trusted users only and enforce strong authentication and access controls to minimize the risk of credential compromise. Implement input validation and sanitization controls on user-supplied Git URLs where possible, or restrict the sources of Git repositories to trusted internal servers. Monitor logs for unusual git ls-remote command invocations or suspicious argument patterns indicative of injection attempts. In Kubernetes/OpenShift environments, enforce the principle of least privilege on service accounts and rotate tokens regularly. Employ network segmentation to isolate automation infrastructure from critical cluster components. Consider deploying runtime security tools that can detect anomalous process executions or command injections on EDA worker nodes. Conduct regular security audits and penetration testing focused on automation platforms and container orchestration environments. Finally, educate administrators and users about the risks of credential compromise and the importance of secure Git repository management.

Description

A flaw was found in Ansible Automation Platform’s EDA component where user-supplied Git URLs are passed unsanitized to the git ls-remote command. This vulnerability allows an authenticated attacker to inject arguments and execute arbitrary commands on the EDA worker. In Kubernetes/OpenShift environments, this can lead to service account token theft and cluster access.

References

Community reviews

Loading reviews…