CVE-2026-12726: Awx: automation-controller: awx: github webhook second-order ssrf via unvalidated statuses_url exfiltrates pat credential
A flaw was found in the AWX GitHub webhook integration. When a GitHub pullrequest webhook is received, GithubWebhookReceiver.geteventstatusapi() in awx/api/views/webhooks.py returns pullrequest.statusesurl from the request body without validation. The value is stored in job extra variables as awxwebhookstatusapi and later used by WebhookMixin.updatewebhookstatus() in awx/main/models/mixins.py as the callback URL when posting job status updates. If a job template is configured with webhookservice=github and a GitHub Personal Access Token credential as webhookcredential, the controller sends that token in the Authorization header when POSTing to the stored callback URL on job completion. Although the controller is designed to post commit status updates back to GitHub, it does not restrict the callback URL to trusted GitHub API endpoints. An attacker who can submit a forged webhook request with a valid HMAC-SHA1 signature for the target job template's webhookkey can supply an attacker-controlled statusesurl and cause exfiltration of the configured GitHub PAT when the triggered job completes. Normal GitHub webhook deliveries do not allow arbitrary contributors to control statusesurl; exploitation requires knowledge of the per-template webhook shared secret or privileged access to retrieve it from the controller. Upstream: https://github.com/ansible/awx Affected files: - awx/api/views/webhooks.py (GithubWebhookReceiver.geteventstatusapi) - awx/main/models/mixins.py (WebhookMixin.updatewebhookstatus)
Other sources
A flaw was found in the AWX GitHub webhook integration. When processing GitHub pullrequest webhooks, the controller stores the pullrequest.statusesurl value from the webhook payload without validating that it points to a trusted GitHub API endpoint. If a job template is configured with a GitHub Personal Access Token as its webhook credential, the controller later POSTs that token to the stored callback URL when posting job status updates. An attacker who can submit a correctly signed forged webhook using the job template's webhookkey can redirect the callback to an attacker-controlled URL and exfiltrate the configured GitHub PAT.
— MITRE
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-12726?
CVE-2026-12726 has a medium severity rating of 6.3.
How do I fix CVE-2026-12726?
To mitigate CVE-2026-12726, ensure that the statuses_url in GitHub webhook payloads is validated against trusted GitHub API endpoints.
What type of vulnerability is CVE-2026-12726?
CVE-2026-12726 is classified as a Server-Side Request Forgery (SSRF) vulnerability.
What impact does CVE-2026-12726 have on AWX automation-controller?
CVE-2026-12726 allows for the exfiltration of personal access token credentials via unvalidated GitHub webhook URLs.
When was CVE-2026-12726 published?
CVE-2026-12726 was published on June 19, 2026.