CVE-2026-12726

MEDIUMPre-NVD 6.36.3
EchelonGraph scoreHIGH confidence

Score 6.3 from GitHub Security Advisory published 2026-06-19. a secondary CVSS source baseline 6.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
6.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.3Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
6.3
EG Score
6.3(high)
EPSS
10.5%
KEV
Not listed

Published

June 19, 2026

Last Modified

June 22, 2026

Advisory Details (2)

Auto-updated Jun 22, 2026
Patch available. Sources: redhat.
redhat

2490796 – (CVE-2026-12726) CVE-2026-12726 awx: automation-controller: awx: GitHub webhook second-order SSRF via unvalidated statuses_url exfiltrates PAT credential

https://bugzilla.redhat.com/show_bug.cgi?id=2490796
redhat Patch Available

cve-details

https://access.redhat.com/security/cve/CVE-2026-12726

Vendor Advisories for CVE-2026-12726(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 20× in last 7d / 48× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-06 16:27 UTCEPSS rescore
  2. 2026-07-06 09:30 UTCEG score recompute
  3. 2026-07-06 09:30 UTCGHSA enrichment
  4. 2026-07-06 02:23 UTCEPSS rescore
  5. 2026-07-05 06:46 UTCEG score recompute
  6. 2026-07-05 06:46 UTCGHSA enrichment
  7. 2026-07-05 02:30 UTCEPSS rescore
  8. 2026-07-05 02:30 UTCEPSS rescore
  9. 2026-07-04 06:31 UTCEPSS rescore
  10. 2026-07-04 04:19 UTCEG score recompute
  11. 2026-07-04 04:19 UTCGHSA enrichment
  12. 2026-07-03 01:18 UTCEG score recompute
  13. 2026-07-03 01:17 UTCGHSA enrichment
  14. 2026-07-01 22:58 UTCEG score recompute
  15. 2026-07-01 22:58 UTCGHSA enrichment
  16. 2026-07-01 15:06 UTCEPSS rescore
  17. 2026-07-01 15:06 UTCEPSS rescore
  18. 2026-06-30 23:22 UTCEPSS rescore
  19. 2026-06-30 20:42 UTCEG score recompute
  20. 2026-06-30 20:42 UTCGHSA enrichment
  21. 2026-06-29 18:16 UTCEG score recompute
  22. 2026-06-29 18:16 UTCGHSA enrichment
  23. 2026-06-29 14:06 UTCEPSS rescore
  24. 2026-06-28 15:58 UTCEG score recompute
  25. 2026-06-28 15:58 UTCGHSA enrichment
Show 23 more
  1. 2026-06-28 14:07 UTCEPSS rescore
  2. 2026-06-28 04:56 UTCEPSS rescore
  3. 2026-06-28 04:56 UTCEPSS rescore
  4. 2026-06-27 13:42 UTCEG score recompute
  5. 2026-06-27 13:41 UTCGHSA enrichment
  6. 2026-06-27 03:08 UTCEPSS rescore
  7. 2026-06-26 11:25 UTCEG score recompute
  8. 2026-06-26 11:24 UTCGHSA enrichment
  9. 2026-06-25 13:49 UTCEPSS rescore
  10. 2026-06-25 09:07 UTCEG score recompute
  11. 2026-06-25 09:07 UTCGHSA enrichment
  12. 2026-06-24 14:05 UTCEPSS rescore
  13. 2026-06-24 06:51 UTCEG score recompute
  14. 2026-06-24 06:51 UTCGHSA enrichment
  15. 2026-06-23 21:32 UTCEPSS rescore
  16. 2026-06-23 04:34 UTCEG score recompute
  17. 2026-06-23 04:34 UTCGHSA enrichment
  18. 2026-06-22 02:18 UTCEG score recompute
  19. 2026-06-22 02:17 UTCGHSA enrichment
  20. 2026-06-20 23:56 UTCEG score recompute
  21. 2026-06-20 23:56 UTCGHSA enrichment
  22. 2026-06-19 21:37 UTCEG score recompute
  23. 2026-06-19 21:37 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-12726?
CVE-2026-12726 is a medium vulnerability published on June 19, 2026. A flaw was found in the AWX GitHub webhook integration. When processing GitHub pullrequest webhooks, the controller stores the pullrequest.statusesurl 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…
When was CVE-2026-12726 disclosed?
CVE-2026-12726 was first published in the National Vulnerability Database on June 19, 2026, with the most recent update on June 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-12726 actively exploited?
CVE-2026-12726 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 10.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-12726?
CVE-2026-12726 has a CVSS v3 base score of 6.3 (NVD).
How do I remediate CVE-2026-12726?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-12726, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-12726

Explore →

Is Your Infrastructure Affected by CVE-2026-12726?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.