Skip to main content
Menu
CVEs

CVE

Red Hat Ansible Automation Platform 2 missing authorization exposes webhook tokens in AWX

CVE-2026-126642EUVD-2026-124330

6.5MediumCNA
Exploited
No known exploitation
Fix
See vendor advisory
Who is exposed
Not reported
Published
Last modified
Reference
Last checked
0.28% · 20th percentile
25/100 · provisional
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: no
  • Technical impact: partial

Summary

AWX, the automation controller component of Red Hat Ansible Automation Platform 2, has a flaw that lets a low-privileged user, reached over the network, attach a webhook token credential they are not allowed to use to their own job template or workflow job template. When a webhook event later fires, AWX sends the victim's token to a destination the attacker can influence, exposing another user's personal access token.

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

Read the original 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.

cve.now Index

25Pcve.now Index 25 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure3/25Reachable over the network · Unknown: No advisory context yet
  • Reach10/20Shipped in major Linux distributions
  • Severity6.5/10CVSS 6.5
  • No patch5/5No fixed version listed; see vendor advisory

What would change the score

  • Would score about 80 if added to CISA KEV
  • Would score about 75 if CISA's SSVC rates exploitation active
  • Would score about 44 if advisories confirm default setups are exposed

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-126642 (Awx: webhook credential assignment omits use_role check, exposing another user's token), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-126642 (entry last updated 2026-11-12):
Affected:
- Red Hat Red Hat Ansible Automation Platform 2: version range not reported
- Red Hat Red Hat Ansible Automation Platform 2: version range not reported
- Red Hat Red Hat Ansible Automation Platform 2: version range not reported
- Red Hat Red Hat Ansible Automation Platform 2: version range not reported
- Red Hat Red Hat Ansible Automation Platform 2: version range not reported
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-126642 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126642 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://bugzilla.redhat.com/show_bug.cgi?id=2571729
- https://access.redhat.com/security/cve/CVE-2026-126642
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-126642
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-126642"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  4. Record last updated

Affected versions

  • ansible-automation-platform-24/controller-rhel8

    Version range not reported

  • ansible-automation-platform-25/controller-rhel8

    Version range not reported

  • ansible-automation-platform-26/controller-rhel9

    Version range not reported

  • ansible-automation-platform-27/controller-rhel9

    Version range not reported

  • automation-controller

    Version range not reported

Evidence 4

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Write-ups · 1

Establishes: Technical detail and context.

  1. Report

Other links · 1

  1. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.