RHSA-2026:59137HighCVSS 8.8

Red Hat Security Advisory: Red Hat Ansible Automation Platform 2.7 Product Security and Bug Fix Update

Published
August 24, 2026
Last Modified
August 24, 2026

🔗 CVE IDs covered (2)

CVE-2026-15307 →CVE-2026-52902 →

📋 Description

CVE-2026-15307 — django: Django: Remote code execution via GeoDjango spatial lookups CVE-2026-52902 — awxkit: path traversal via YAML !include directive

🎯 Affected products44

  • Red Hat Ansible Automation Platform 2.7 for RHEL 10
  • Red Hat Ansible Automation Platform 2.7 for RHEL 9
  • ansible-creator-0:26.8.0-2.el10ap.noarch as a component of Red Hat Ansible Automation Platform 2.7 for RHEL 10
  • ansible-creator-0:26.8.0-2.el10ap.src as a component of Red Hat Ansible Automation Platform 2.7 for RHEL 10
  • ansible-creator-0:26.8.0-2.el9ap.noarch as a component of Red Hat Ansible Automation Platform 2.7 for RHEL 9
  • ansible-creator-0:26.8.0-2.el9ap.src as a component of Red Hat Ansible Automation Platform 2.7 for RHEL 9
  • ansible-dev-environment-0:26.8.0-1.el10ap.noarch as a component of Red Hat Ansible Automation Platform 2.7 for RHEL 10
  • ansible-dev-environment-0:26.8.0-1.el10ap.src as a component of Red Hat Ansible Automation Platform 2.7 for RHEL 10
  • ansible-dev-environment-0:26.8.0-1.el9ap.noarch as a component of Red Hat Ansible Automation Platform 2.7 for RHEL 9
  • ansible-dev-environment-0:26.8.0-1.el9ap.src as a component of Red Hat Ansible Automation Platform 2.7 for RHEL 9
  • ansible-dev-tools+server-0:26.8.0-1.el10ap.noarch as a component of Red Hat Ansible Automation Platform 2.7 for RHEL 10
  • ansible-dev-tools+server-0:26.8.0-1.el9ap.noarch as a component of Red Hat Ansible Automation Platform 2.7 for RHEL 9
  • ansible-dev-tools-0:26.8.0-1.el10ap.noarch as a component of Red Hat Ansible Automation Platform 2.7 for RHEL 10
  • ansible-dev-tools-0:26.8.0-1.el10ap.src as a component of Red Hat Ansible Automation Platform 2.7 for RHEL 10
  • ansible-dev-tools-0:26.8.0-1.el9ap.noarch as a component of Red Hat Ansible Automation Platform 2.7 for RHEL 9
  • ansible-dev-tools-0:26.8.0-1.el9ap.src as a component of Red Hat Ansible Automation Platform 2.7 for RHEL 9
  • ansible-lint-0:26.8.0-1.el10ap.noarch as a component of Red Hat Ansible Automation Platform 2.7 for RHEL 10
  • ansible-lint-0:26.8.0-1.el10ap.src as a component of Red Hat Ansible Automation Platform 2.7 for RHEL 10
  • ansible-lint-0:26.8.0-1.el9ap.noarch as a component of Red Hat Ansible Automation Platform 2.7 for RHEL 9
  • ansible-lint-0:26.8.0-1.el9ap.src as a component of Red Hat Ansible Automation Platform 2.7 for RHEL 9
  • ansible-navigator-0:26.8.0-2.el10ap.noarch as a component of Red Hat Ansible Automation Platform 2.7 for RHEL 10
  • ansible-navigator-0:26.8.0-2.el10ap.src as a component of Red Hat Ansible Automation Platform 2.7 for RHEL 10
  • ansible-navigator-0:26.8.0-2.el9ap.noarch as a component of Red Hat Ansible Automation Platform 2.7 for RHEL 9
  • ansible-navigator-0:26.8.0-2.el9ap.src as a component of Red Hat Ansible Automation Platform 2.7 for RHEL 9
  • automation-controller-cli-0:4.8.6-1.el10ap.noarch as a component of Red Hat Ansible Automation Platform 2.7 for RHEL 10
  • automation-controller-cli-0:4.8.6-1.el10ap.src as a component of Red Hat Ansible Automation Platform 2.7 for RHEL 10
  • automation-controller-cli-0:4.8.6-1.el9ap.noarch as a component of Red Hat Ansible Automation Platform 2.7 for RHEL 9
  • automation-controller-cli-0:4.8.6-1.el9ap.src as a component of Red Hat Ansible Automation Platform 2.7 for RHEL 9
  • molecule-0:26.8.0-1.el10ap.noarch as a component of Red Hat Ansible Automation Platform 2.7 for RHEL 10
  • molecule-0:26.8.0-1.el10ap.src as a component of Red Hat Ansible Automation Platform 2.7 for RHEL 10
  • +14 more not shown

✅ Remediation

For details on how to apply this update, refer to Ansible Automation Platform documentation. Workaround: Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability. Workaround: The following practices would help for avoiding exposure to this flaw: 1) Prioritize the default JSON import format instead of YAML. 2) Avoid importing YAML files from untrusted sources.

🔗 References (7)