PoC Monitor
← All CVEs
CVE-2026-71366published 24 Aug 2026 15:42 UTCData: JSON · API

Red Hat Ansible Automation Platform 2.5 for RHEL 8

Awx: notification backends allow ssrf and credential leakage

A server-side request forgery (SSRF) vulnerability was found in multiple AWX notification backends. The webhook, Mattermost, Rocket.Chat, and Grafana notification backends use notification template URLs as direct HTTP request targets without validating the target address against private, loopback, or reserved IP ranges. An organization notification administrator can create notification templates pointing to internal or loopback addresses, causing the AWX control node to issue HTTP requests to services that are not externally accessible. Additionally, the webhook notification backend follows HTTP redirects and resends configured Basic Authentication credentials to redirect targets regardless of host change, allowing an attacker to exfiltrate notification credentials by redirecting to an attacker-controlled host. The Grafana backend sends its API key in the Authorization header to the configured target URL.

First public PoC None yetno public PoC found
Public PoCs00 on GitHub
CVSS7.7high · scored by CNA · CWE-918
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

Red Hat Red Hat Ansible Automation Platform 2.5 for RHEL 8

    Fixed in 0:4.6.32-1.el8ap

    Red Hat Red Hat Ansible Automation Platform 2.5 for RHEL 8

      Fixed in 0:4.6.32-1.el8ap

      Red Hat Red Hat Ansible Automation Platform 2.5 for RHEL 9

        Fixed in 0:4.6.32-1.el9ap

        Red Hat Red Hat Ansible Automation Platform 2.5 for RHEL 9

          Fixed in 0:4.6.32-1.el9ap

          Red Hat Red Hat Ansible Automation Platform 2.6 for RHEL 9

            Fixed in 0:4.7.16-1.el9ap

            Red Hat Red Hat Ansible Automation Platform 2.6 for RHEL 9

              Fixed in 0:4.7.16-1.el9ap

              Red Hat Red Hat Ansible Automation Platform 2.6

                Fixed in 1787244009

                Red Hat Red Hat Ansible Automation Platform 2.7

                  Fixed in 1787220257

                  Mitigation

                  Upgrade Red Hat Ansible Automation Platform 2.5 for RHEL 8 to 0:4.6.32-1.el8ap or later.

                  Upgrade Red Hat Ansible Automation Platform 2.5 for RHEL 8 to 0:4.6.32-1.el8ap or later.

                  Upgrade Red Hat Ansible Automation Platform 2.5 for RHEL 9 to 0:4.6.32-1.el9ap or later.

                  Upgrade Red Hat Ansible Automation Platform 2.5 for RHEL 9 to 0:4.6.32-1.el9ap or later.

                  Upgrade Red Hat Ansible Automation Platform 2.6 for RHEL 9 to 0:4.7.16-1.el9ap or later.

                  Upgrade Red Hat Ansible Automation Platform 2.6 for RHEL 9 to 0:4.7.16-1.el9ap or later.

                  Upgrade Red Hat Ansible Automation Platform 2.6 to 1787244009 or later.

                  Upgrade Red Hat Ansible Automation Platform 2.7 to 1787220257 or later.

                  Workaround

                  There is no complete mitigation for this vulnerability other than applying the update when available. However, the following measures reduce exposure: 1. Restrict the ability to create and modify notification templates to trusted administrators who have legitimate need for this capability. 2. Implement network egress filtering on the Automation Controller nodes to block outbound connections to loopback (127.0.0.0/8), private (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16), and link-local (169.254.0.0/16) address ranges. 3. Monitor notification template configurations for URLs pointing to internal or unusual addresses. 4. Avoid configuring sensitive credentials (Basic Auth, Grafana API keys) in notification templates until the fix is applied. Use notification backends that do not require credentials where possible. 5. Review and audit existing notification templates for URLs pointing to internal services.

                  References

                  1 more

                  Timeline

                  Days relative to CVE publication
                  -2t=0+2+4+6+8CVE published24 Aug 2026 · t = 0

                  No public PoC found yet; not in CISA KEV.

                  PoC repositories

                  Found on GitHub.

                  No PoC repositories found yet.