CVE-2026-71363VulnerabilityPublished 12 Nov 2026

Missing Authentication

Source GCVE Database

Compare

Authoritative record:CVE-2026-71363· Medium 5.3

Not known to be exploited · CVSS 5.3 Medium.

Data as of 12 Nov 2026, 19:48 UTC

CVSS 3.1 base score

5.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	5.3

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

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

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: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
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: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to 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-j7wj-xf6p-vhwp

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

No complete mitigation exists other than applying the update when available. Until a fix is released, reduce exposure by: 1) Restricting network access to the Automation Controller API (/api/) to trusted networks and authenticated clients via firewall or reverse proxy; 2) Configuring a reverse proxy or web application firewall to block requests to /api/debug/* paths; 3) For Ansible Automation Platform 2.5 and later, ensuring the Automation Controller API is not directly accessible, bypassing the Platform Gateway. Customers should monitor Red Hat advisories for patch availability.

Description

A vulnerability in AWX allows unauthenticated remote attackers to access debug API endpoints that trigger scheduler operations acquiring database advisory locks and opening transactions. This can lead to resource exhaustion and degraded service availability due to lock contention. The flaw arises because these debug endpoints are registered unconditionally and use permissive access controls. While the vulnerability does not allow data compromise, it can cause service degradation under sustained attack. No complete mitigation exists except applying a future update. Interim mitigations include restricting network access and blocking debug API paths.

Impact

The vulnerability allows unauthenticated remote attackers to invoke scheduler operations that acquire database advisory locks and open transactions, leading to resource exhaustion and degraded service availability due to lock contention. There is no impact on confidentiality or integrity. The practical impact is limited to service degradation under sustained attack conditions.

Summary

The vulnerability in AWX involves debug API endpoints (/api/debug/task_manager/, /api/debug/dependency_manager/, /api/debug/workflow_manager/) that are registered without authentication and use the AllowAny permission class with _ignore_model_permissions=True. This allows unauthenticated attackers to repeatedly invoke scheduler operations that acquire database advisory locks and open transactions, potentially causing resource exhaustion and degraded availability. The scheduler serializes concurrent invocations, limiting resource consumption per request but enabling lock contention under sustained attack. Red Hat rates the impact as moderate, with the primary effect being service degradation rather than data compromise. In Red Hat Ansible Automation Platform 2.5 and later, an additional authentication layer (Platform Gateway) may prevent unauthenticated access depending on deployment.

CWE-306Missing Authentication for Critical Functionality (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #21OWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources.
Architecture and Design
Divide the software into anonymous, normal, privileged, and administrative areas. Identify which of these areas require a proven user identity, and use a centralized authentication capability.
Architecture and Design
For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks…
Architecture and Design
Where possible, avoid implementing custom, "grow-your-own" authentication routines and consider using authentication capabilities as provided by the surrounding framework, operating system, or environment.
OWASP Cheat Sheets
OWASP Authentication (opens in a new tab)
OWASP ASVS 4.0.3
V1.2.3 (opens in a new tab)
V1.2.2 (opens in a new tab)
V1.2.4 (opens in a new tab)
Attack patterns
Choosing Message Identifier (opens in a new tab)
Force the System to Reset Values (opens in a new tab)
Using Unpublished Interfaces or Functionality (opens in a new tab)
Cross Site Request Forgery (opens in a new tab)
Communication Channel Manipulation (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, 19:48 UTC

WeaknessesCWE-306

Technical details

References

Community reviews

Related threats