Vulnerability 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.
CVSS Score
HIGH
Related Weaknesses (CWE)
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
FAQ
What is CVE-2026-71365?
CVE-2026-71365 is a vulnerability with a CVSS score of 7.7 (HIGH). 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_reques...
How severe is CVE-2026-71365?
CVE-2026-71365 has been rated HIGH with a CVSS base score of 7.7/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-71365?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.