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.

Executive Summary

Technical Details

Mitigations

References

Additional Metadata

{
  "score": "7.7",
  "pubDate": "2026-08-18T16:18:16.157Z",
  "pubdate": "2026-08-18T16:18:16.157Z",
  "executiveSummary": "A server-side request forgery (SSRF) vulnerability has been identified in the AWX webhook status callback mechanism, specifically when processing GitHub pull request webhooks. The flaw allows an authenticated administrator to manipulate status callback URLs, resulting in unauthorized requests directed at arbitrary external or internal endpoints.\nThe primary impact of this vulnerability is sensitive credential leakage. When AWX initiates the status update request to the attacker-controlled destination, it includes the configured Git Personal Access Token (PAT) within the Authorization header. This exposes critical authentication secrets to potential threat actors.\nThe affected system is AWX utilizing webhook-enabled job templates. Exploitation requires administrative privileges on a webhook-enabled job template, allowing the attacker to read the template's webhook signing key and forge a valid, signed GitHub webhook payload containing a malicious pull_request.statuses_url.\nThe risk implications are significant, as successful exploitation bridges internal network boundaries via SSRF and compromises sensitive Git provider integration secrets. This enables lateral movement within internal infrastructures and unauthorized access to external Git repositories associated with the leaked credentials.",
  "technicalDetails": "The root cause of the vulnerability resides in insufficient input validation within the AWX webhook status callback mechanism. When AWX ingests incoming GitHub pull request webhooks, it extracts the status callback URL directly from the pull_request.statuses_url field of the incoming payload. The application fails to validate the target host against the expected Git provider domain, blindly persisting the untrusted URL within job extra variables.\nThe vulnerable component is the webhook processing pipeline responsible for handling GitHub pull request events and scheduling subsequent status updates. The attack flow proceeds through a series of distinct technical steps. First, an attacker leverages an administrative role on a webhook-enabled job template to retrieve the template's webhook signing key. Armed with this cryptographic secret, the attacker crafts and signs a fraudulent GitHub webhook payload where the pull_request.statuses_url points to an attacker-controlled listener or an internal network resource.\nUpon receiving the forged webhook, AWX processes and stores the arbitrary statuses_url. When the associated job reaches a state requiring a status update, AWX initiates an outbound HTTP POST request to the stored URL. Crucially, the payload generated and transmitted by AWX incorporates the configured Git Personal Access Token (PAT) within the Authorization header.\nThe authentication and privilege requirements mandate that the attacker possesses an admin role on a webhook-enabled job template. Network exposure involves the capability of the AWX server to dispatch outbound HTTP/HTTPS requests to arbitrary destinations specified in the manipulated webhook data, thereby bypassing network segmentation controls and facilitating potential internal reconnaissance or data exfiltration."
}