Skip to content
statance
MenuClose
Log inStart for free ↗
high · CVSS 7.7

CVE-2026-71365

Awx: webhook status callback ssrf leaks the git pat

Published 18 Aug 2026 · Source updated 4 Nov 2026 · Retrieved 2026-11-06 13:18 UTC

Monitor this CVE ↗Full CVE monitoring on Pro and Business

What happened?

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.

Description supplied by CVE Program. Formatting is simplified; follow the original advisory for full details.

Affected software and versions

Source-provided software and version information
SoftwareVersion informationFixed version
automation-controllerRed Hatunaffected: 0:4.6.32-1.el8ap to < *See vendor advisory
automation-controllerRed Hatunaffected: 0:4.6.32-1.el8ap to < *See vendor advisory
automation-controllerRed Hatunaffected: 0:4.6.32-1.el9ap to < *See vendor advisory
automation-controllerRed Hatunaffected: 0:4.6.32-1.el9ap to < *See vendor advisory
automation-controllerRed Hatunaffected: 0:4.7.16-1.el9ap to < *See vendor advisory
automation-controllerRed Hatunaffected: 0:4.7.16-1.el9ap to < *See vendor advisory
ansible-automation-platform-26/controller-rhel9Red Hatunaffected: 1787244009 to < *See vendor advisory
ansible-automation-platform-27/controller-rhel9Red Hatunaffected: 1787220257 to < *See vendor advisory

Version information comes from the source record and can include unaffected products and exceptions. Distribution packages may contain backported fixes: an older upstream version alone does not prove a server is affected.

Is it being exploited?

This CVE was not listed in the CISA catalogue at our last retrieval. This does not establish that exploitation is absent.

CISA data retrieved 2026-11-06 16:38 UTC. Check CISA ↗

How to respond

  1. Confirm the product, installed package version, and any configuration requirements in the vendor advisory.
  2. Follow the vendor’s remediation or workaround guidance in the references below. Structured fixed-version data is unavailable here; the publisher’s description may include a fix or workaround.
  3. Restart affected services if required, then verify the running version. Known exploitation may warrant investigation as well as patching.

Sources and remediation references

This public advisory does not determine whether a particular server is affected. Records are refreshed as sources change; verify urgent decisions against the original advisory.

← Browse the public CVE feed