GPU VulnDB

Database/Control plane, storage & DevOps

AWX: template admin can attach another user's webhook token and have it sent to a destination they control

CVSS 6.5CVE-2026-126642Control plane, storage & DevOpscurated

Impact

When a job template or workflow job template is assigned a webhook_credential, AWX does not check that the caller has use permission on that credential. A user who administers their own template can therefore attach someone else's webhook token, for example a GitLab personal access token. A later webhook event makes AWX decrypt that token and send it in a request header to a status URL taken from the event payload, which the attacker can influence. The attacker ends up holding the victim's token and can do whatever it permits, which in an automation controller that configures fleet nodes can include pushing to infrastructure repositories.

Who can reach it

An authenticated AWX/AAP user who can administer a job template or workflow job template and use its project and inventory, over the network. They also need to trigger or influence a webhook event.

What to do

Apply the Red Hat Ansible Automation Platform 2 update listed in the Red Hat advisory. The record names no fixed version. In the meantime, audit the webhook_credential assignments on templates and rotate any tokens attached to templates whose administrators should not have them.

References

Related entries

All Control plane, storage & DevOps entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.