The vulnerability exists in the AWX GitHub webhook integration of Red Hat Ansible Automation Platform 2. When processing GitHub pull_request webhooks, the controller stores the pull_request.statuses_url from the webhook payload without verifying that it points to a trusted GitHub API endpoint. If a job template uses a GitHub Personal Access Token as its webhook credential, the controller later posts that token to the stored callback URL when updating job status. An attacker who can submit a correctly signed forged webhook using the job template's webhook_key can redirect this callback to an attacker-controlled URL, thereby exfiltrating the configured GitHub PAT. The CVSS v3.1 score is 6.3 (medium severity), reflecting network attack vector, high attack complexity, low privileges required, no user interaction, scope change, high confidentiality impact, and no integrity or availability impact. No patch or official remediation level has been confirmed in the vendor advisory as of the published date.

An attacker able to submit a forged webhook with a valid webhook_key can cause the system to send the GitHub Personal Access Token configured in the job template to an attacker-controlled URL. This leads to the exfiltration of sensitive credentials, potentially compromising GitHub resources accessible by that token. The vulnerability impacts confidentiality but does not affect integrity or availability of the system.

Patch status is not yet confirmed — check the Red Hat advisory at https://access.redhat.com/security/cve/CVE-2026-12726 for current remediation guidance. Until a fix is available, consider restricting webhook_key distribution, validating callback URLs manually, or disabling GitHub webhook integrations that use Personal Access Tokens as credentials to reduce risk.