CVE-2026-126642 Awx: webhook credential assignment omits use_role check, exposing another user's token

Medium 6.5 Published Updated

A job template admin can attach another user's webhook token and steal it via webhook events, gaining that user's permissions; AWX operators should care.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Over the internet
Victim action needed
Not needed
Harmful if only installed
No
Needs a specific call
No
Fix
None listed

What is CVE-2026-126642?

CVE-2026-126642 is a medium-severity missing authorization vulnerability in Red Hat Ansible Automation Platform 2, published on 12 Nov 2026. Any signed-in user can exploit it over the network, with no action from the victim.

Official description

An incorrect authorization flaw was found in AWX, the automation controller component of Red Hat Ansible Automation Platform. The API access classes for JobTemplate and WorkflowJobTemplate do not check the caller's Credential use_role when assigning the single-valued webhook_credential foreign key: JobTemplateAccess.can_add/can_change and WorkflowJobTemplateAccess.can_change in awx/main/access.py omit the check_related('webhook_credential', Credential, ..., role_field='use_role') call that UnifiedCredentialsMixin.can_attach performs for the normal many-to-many credentials relationship, and the serializer validates only the credential's type and namespace. A user who may administer their own job template (or workflow job template) and use its project and inventory can therefore attach a webhook token credential (for example a GitLab token) that they do not have use permission on. The template administrator can retrieve the template's webhook key; a subsequent webhook event causes AWX to decrypt the attached token and send it in the request header (for GitLab, PRIVATE-TOKEN) to a status URL derived from the event payload, disclosing the victim's token to a destination the attacker can influence. This may disclose another user's personal access token and allow whatever actions that token permits.

Weakness: CWE-862

Which versions are affected by CVE-2026-126642?

An affected version is exposed as installed. No special setting or call is needed.

How do I fix CVE-2026-126642?

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

Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.

Is CVE-2026-126642 being exploited?

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

Sources

Also known as GHSA-c92q-w8v5-r4hp, UBUNTU-CVE-2026-126642.

Is CVE-2026-126642 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free