Credential disclosure via unvalidated webhook callback URL
Published Jun 19, 2026 · Updated Jun 19, 2026
SSRF in the GitHub webhook integration in Red Hat Ansible Automation Platform 2 allows remote authenticated users to steal GitHub tokens. The controller stores an unvalidated pull_request.statuses_url and later posts the configured GitHub PAT to that attacker-selected callback. A valid webhook_key, a correctly signed forged webhook, and a template configured with a GitHub PAT are required; the resulting request discloses that token.
Summary
What happened
SSRF in the GitHub webhook integration in Red Hat Ansible Automation Platform 2 allows remote authenticated users to steal GitHub tokens. The controller stores an unvalidated pull_request.statuses_url and later posts the configured GitHub PAT to that attacker-selected callback. A valid webhook_key, a correctly signed forged webhook, and a template configured with a GitHub PAT are required; the resulting request discloses that token.
The record
- CVE
- CVE-2026-12726
- Published
- Jun 19, 2026
- Updated
- Jun 19, 2026
- Vendor
- 389 Directory Server
- Product
- Red Hat Ansible Automation Platform
- Classifications
- CWE-918, T1528
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 19, 2026CVE publishedPublication date reported by the CVE source.
- Jun 19, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo