# CVE-2026-12726: Server-side request forgery in Red Hat Ansible Automation Platform 2

> Attackers can exfiltrate GitHub Personal Access Tokens by forging webhooks to redirect status updates to malicious URLs in AWX.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Jun 2026
- **Updated:** 22 Jun 2026
- **Also known as:** GHSA-w8qh-qh69-53cx

## What is CVE-2026-12726?

CVE-2026-12726 is a medium-severity server-side request forgery vulnerability in Red Hat Ansible Automation Platform 2, published on 19 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-12726?


## How do I fix CVE-2026-12726?

No fix has been published for CVE-2026-12726 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-12726 being exploited?

There is no known exploitation of CVE-2026-12726 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-12726 and fix it if it is affected.

What it is: CVE-2026-12726 is a medium-severity server-side request forgery vulnerability in Red Hat Ansible Automation Platform 2, published on 19 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-12726 in the wild and no public exploit code.

Affected product: Red Hat Ansible Automation Platform 2. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-12726/ (Markdown: https://insights.sbomify.com/CVE-2026-12726/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-12726
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-12726
- OSV: https://osv.dev/vulnerability/CVE-2026-12726

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-12726/
Summaries are generated and may contain mistakes; the official description above is the record.