Red Hat Ansible Automation Platform 2 Trusted GitHub API Endpoint pull_request.statuses_url server-side request forgery

Summaryinfo

A vulnerability was found in Red Hat Ansible Automation Platform 2. It has been declared as critical. Impacted is an unknown function of the component Trusted GitHub API Endpoint. Such manipulation of the argument pull_request.statuses_url leads to server-side request forgery. This vulnerability is documented as CVE-2026-12726. The attack can be executed remotely. There is not any exploit available.

Detailsinfo

A vulnerability, which was classified as critical, has been found in Red Hat Ansible Automation Platform 2 (version now known). Affected by this issue is some unknown processing of the component Trusted GitHub API Endpoint. The manipulation of the argument pull_request.statuses_url with an unknown input leads to a server-side request forgery vulnerability. Using CWE to declare the problem leads to CWE-918. The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. Impacted is confidentiality, integrity, and availability. CVE summarizes:

A flaw was found in the AWX GitHub webhook integration. When processing GitHub pull_request webhooks, the controller stores the pull_request.statuses_url value from the webhook payload without validating that it points to a trusted GitHub API endpoint. If a job template is configured with a GitHub Personal Access Token as its webhook credential, the controller later POSTs that token to the stored callback URL when posting job status updates. An attacker who can submit a correctly signed forged webhook using the job template's webhook_key can redirect the callback to an attacker-controlled URL and exfiltrate the configured GitHub PAT.

The advisory is shared for download at access.redhat.com. This vulnerability is handled as CVE-2026-12726 since 06/19/2026. The exploitation is known to be difficult. The attack may be launched remotely. There are known technical details, but no exploit is available. The current price for an exploit might be approx. USD $5k-$25k (estimation calculated on 06/20/2026).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-38065). Once again VulDB remains the best source for vulnerability data.

Productinfo

Type

• Automation Software

Vendor

• Red Hat

Name

• Ansible Automation Platform 2

License

• open-source

Website

• Vendor: https://www.redhat.com/

CPE 2.3info

• 🔒

CPE 2.2info

• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion