VulnerabilityPublished 12 Nov 2026

CVE-2026-71367: AWX's WebSocket consumer · Incorrect Authorization Vulnerability Was Found

Source GCVE Database

Compare

Authoritative record:CVE-2026-71367· Medium 4.3

Not known to be exploited · CVSS 4.3 Medium.

Data as of 12 Nov 2026, 16:35 UTC

CVSS 3.1 base score

4.3Medium

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CNA (redhat)	CVSS 3.1	4.3

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 12 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 12 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-chf8-h4m7-hwh4

What to do

Affected software

Product	Affected	Fixed in
Red Hat Ansible Automation Platform 2ansible-automation-platform-26/controller-rhel9	Affected–	Fixed in–
Red Hat Ansible Automation Platform 2ansible-automation-platform-27/controller-rhel9	Affected–	Fixed in–
Red Hat Ansible Automation Platform 2automation-controller	Affected–	Fixed in–

AI-suggested

A complete fix is not yet available; apply the official update when released. Meanwhile, reduce exposure by restricting user account creation to necessary personnel and auditing user organization memberships in multi-organization deployments. If using a reverse proxy or load balancer, restrict WebSocket upgrade requests to authenticated sessions with legitimate use cases. Managed service providers should consider network-level WebSocket filtering at the service mesh layer. Additionally, monitor WebSocket subscription activity for unauthorized subscriptions to broadcast groups outside user organization scope.

Description

CVE-2026-71367 is an incorrect authorization vulnerability in AWX's WebSocket consumer that allows authenticated users in multi-organization deployments to subscribe to global broadcast groups without proper permission checks. This leads to unauthorized access to real-time job status metadata across organizations, including job IDs, status changes, timestamps, and infrastructure details. The vulnerability does not expose full job outputs or credentials. It mainly impacts multi-organization and managed service deployments, while single-organization setups are not practically affected.

Impact

The vulnerability allows unauthorized disclosure of job metadata across organizational boundaries in multi-organization AWX deployments. This includes job IDs, status changes, timestamps, and infrastructure topology details such as instance group names. The information disclosure is limited and does not include sensitive data like full job outputs, playbook content, or credentials. Single-organization deployments are not affected in practice since all users share the same job visibility. Managed service deployments face a higher risk due to cross-tenant exposure of job activity patterns and infrastructure details. There is no known exploitation in the wild.

Summary

The vulnerability exists because the consumer_access() function in AWX's WebSocket consumer enforces access controls only for object-level event groups but fails to restrict subscriptions to global broadcast groups such as 'jobs-status_changed'. As a result, authenticated users can subscribe to these global groups without verification of their permissions to view the associated resources. In multi-organization deployments, this bypasses organization isolation enforced by the REST API, allowing low-privilege users to receive job metadata from all organizations. The leaked information includes job IDs, status transitions, timestamps, and instance group names but excludes sensitive data like job outputs or credentials. Red Hat assesses this as a moderate impact vulnerability for on-premise deployments, with higher impact in managed service environments due to cross-tenant information disclosure. No complete mitigation exists other than applying a forthcoming update. Interim measures include restricting user account creation, auditing memberships, filtering WebSocket upgrade requests, and monitoring subscription activity.

CWE-863Incorrect Authorization (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #17OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.
Architecture and Design
Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries.
Architecture and Design
Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.8 (opens in a new tab)
V13.4.2 (opens in a new tab)
V7.2.2 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 12 Nov 2026, 16:35 UTC

WeaknessesCWE-863

Technical details

References

Community reviews

Related threats