dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2026-12726

MEDIUM · 6.3 CVSS v3.1 Published 2026-06-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

AWX's GitHub webhook integration stores the pull_request.statuses_url from webhook payloads without validating it's a trusted GitHub API endpoint. An attacker with the webhook_key can submit a forged webhook with a malicious callback URL. When the job template uses a GitHub PAT as its webhook credential, that token gets POSTed to the attacker-controlled URL during job status updates, resulting in token exfiltration.

MitigationImplement validation to ensure the statuses_url originates from trusted GitHub API endpoints (api.github.com) before storing or using it for callbacks. Consider adding a configuration option to restrict webhook credential usage to specific repositories.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify AWX installation
    Check if AWX is deployed in your environment. This can be done via kubectl get pods -n awx, docker ps, or checking your infrastructure inventory for awx-related services.
    Affected if AWX is not present in your environment
  2. Check for GitHub webhook credential usage
    In the AWX UI, navigate to Resources > Credentials, or use the API: GET /api/v2/credentials/. Look for credentials with credential_type matching 'GitHub PAT' or similar GitHub personal access token types.
    Affected if No credentials of type GitHub PAT exist in your environment
  3. Identify job templates using GitHub webhooks
    In AWX UI, go to Resources > Templates, or use the API: GET /api/v2/job_templates/. Filter for templates where 'webhook_service' is set to 'github' and 'webhook_credential' is not null.
    Affected if No job templates are configured with GitHub webhook service enabled
  4. Inspect stored webhook URLs for untrusted endpoints
    For each job template with GitHub webhooks enabled, examine the related webhook_payload_urls or repository webhook configurations. Check if any stored URLs point to domains other than api.github.com or github.com. Use API: GET /api/v2/job_templates/{id}/ to view webhook related fields.
    Affected if Any job template has a webhook_url pointing to a domain other than github.com or api.github.com
  5. Review recent webhook job events for suspicious activity
    Check the job logs and webhook events in AWX: Jobs > select a job > Stdout tab, or review webhook service logs. Look for POST requests made to non-GitHub domains during job status updates.
    Affected if Webhook callback requests have been made to untrusted or external domains

A user is affected if they have AWX running with GitHub webhook integration enabled on any job template that uses a GitHub PAT as a webhook credential, as the token could be exfiltrated to an attacker-controlled URL.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement validation to ensure the statuses_url originates from trusted GitHub API endpoints (api.github.com) before storing or using it for callbacks. Consider adding a configuration option to restrict webhook credential usage to specific repositories.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-12726 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-12726 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data