GPU VulnDB

Database/Control plane, storage & DevOps

Ansible AWX: notification backends allow SSRF from the control node and leak webhook credentials

CVE-2026-71366Control plane, storage & DevOpscurated

Impact

Notification template URLs are used as direct HTTP request targets with no check against private, loopback or reserved ranges, so an organization notification administrator can make the AWX control node issue requests to anything it can reach. That node normally sits on the management network with routes to BMC and Redfish endpoints, cluster APIs and cloud metadata services that no tenant can reach directly. Two credential leaks compound it: the webhook backend follows redirects and resends its configured Basic Authentication credentials to the redirect target even when the host changes, and the Grafana backend puts its API key in the Authorization header to whatever URL is configured. This is request forgery and credential theft from the automation control plane, not code execution on it.

Who can reach it

Authenticated AWX user holding organization notification-administrator rights (enough to create or edit a notification template), over the network. No access to the AWX host itself.

What to do

Apply the Ansible Automation Platform errata for your stream - RHSA-2026:59135 and RHSA-2026:59136 cover AAP 2.5 on RHEL 8/9 and 2.6 on RHEL 9 - and restart the AWX services. This is control-plane only: no GPU node is drained or rebooted. Until patched, restrict who holds notification-admin on each organization and rotate any Basic Auth or Grafana API credentials already configured in notification templates, since a leak would be silent.

References

Related entries

All Control plane, storage & DevOps entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.