EUVD-2026-85609
GHSA-cvm2-8wp9-2853
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach automation-controller API unauthenticated
-
DeliveryGET /api/v2/ping/
-
ExploitReceive over-serialized mesh inventory
-
ExecutionMap control plane and fingerprint exact versions
-
ImpactSelect targeted follow-on exploit
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V14 - Data Protection System info exposure prevention
|
| Exploitation Conditions | No special conditions - remote unauthenticated exploitation against default configurations of Red Hat Ansible Automation Platform 2 automation-controller. The vulnerable endpoint /api/v2/ping/ is served by ApiV2PingView with an AllowAny permission class, so no authentication, user interaction, or non-default setting is required; the only limiting factor is network reachability of the automation-controller API. Impact is bounded to disclosure of mesh topology and version metadata - the flaw does not expose secrets, credentials, or tenant data, which caps confidentiality impact at Low. |
| Impact | All signals converge on a genuine-but-modest information-disclosure issue, not a top priority. The CVSS 5.3 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N) correctly reflects a remote, unauthenticated, low-complexity read with only low confidentiality impact and no integrity or availability effect - consistent with CWE-497 (exposure of sensitive system information). The vector and description agree: the endpoint is genuinely reachable pre-auth and returns data, so there is no network-vs-local contradiction. No EPSS score, no CISA KEV listing, and no public exploit code were provided, so this is no public exploit identified at time of analysis; there is also no SSVC decision data. Real-world impact is reconnaissance value only: the leak maps the automation-mesh control plane and pins exact software versions, which lowers the cost of a targeted follow-on attack but exposes no secrets, credentials, or tenant data (vendor-stated). Net: legitimately worth patching because it is trivially reachable by anyone who can reach the API, but it is a low-severity fingerprinting/enumeration flaw rather than a direct-compromise vulnerability. |
| Exploit ScenarioDerived | An unauthenticated attacker who can reach the automation-controller API sends a single GET to /api/v2/ping/ and receives the full instance inventory - node hostnames, types, UUIDs, heartbeats, capacities, exact versions, all instance-group names and membership, the install UUID, and the active control node. They use the exact version strings to select version-specific exploits and the topology map to pick the control node as a target. No public exploit code is required; the request is a trivial, low-complexity HTTP call against a default-exposed health endpoint. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 23, 2026
Information disclosure in the automation-controller API of Red Hat Ansible Automation Platform 2 lets any remote unauthenticated party read the automation mesh topology from the health-check endpoint /api/v2/ping/ (CVSS 3.1: 5.3, AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N). Because the ApiV2PingView view is declared with the AllowAny permission class and over-serializes RBAC-gated mesh data into its anonymous response, an attacker needs only network reachability to walk away with node hostnames, node types, UUIDs, heartbeats, capacities, exact software versions, instance-group names and membership, the deployment install UUID, and the identity of the active control node. The exposure is confidentiality-only - no secrets, credentials, or tenant data are involved - and there is no public exploit identified at time of analysis, so this is a genuine but modest reconnaissance-grade issue rather than an urgent one.
RemediationAI
No vendor-released patch was identified at time of analysis, so remediation currently rests on compensating controls rather than an upgrade; the absence of patch data in the provided references is not confirmation that no fix exists, and the Red Hat CVE page (https://access.redhat.com/security/cve/CVE-2026-84712) and Bugzilla record (https://bugzilla.redhat.com/show_bug.cgi?id=2527196) should be monitored for errata and for the exact fixed automation-controller build before scheduling an upgrade. The highest-value control is to stop untrusted clients from reaching /api/v2/ping/ at all: restrict the automation-controller API to management networks with firewall or security-group rules, or require authentication at the reverse proxy for /api/v2/* while leaving the internal path used by health monitors intact - the trade-off is that external load-balancer and synthetic-monitoring probes pointed at the public hostname will start failing and must be repointed to an internal address or an alternate health path. If the endpoint must remain publicly reachable, terminate it at a reverse proxy that rewrites or strips the ping response down to a minimal status body rather than proxying the full serialized payload; this preserves availability of the health check but will silently break any monitoring that parses the removed fields. Version fingerprinting risk can be further reduced by suppressing server and version headers and by treating the exposed inventory as known to an adversary when planning segmentation of mesh nodes and the control node. Finally, because the disclosure is read-only reconnaissance, detection should focus on proxy and API access logs for enumeration of /api/v2/ping/ from external, unauthenticated source addresses, and - given CVSS 5.3 with no public exploit identified at time of analysis - this should be scheduled as a routine hardening item rather than an emergency change.
Affected VersionsENISA
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The affected component is the automation-controller (the AWX-derived control plane) inside Red Hat Ansible Automation Platform 2, exposed here through a Django REST Framework view, ApiV2PingView, that backs the unauthenticated liveness endpoint /api/v2/ping/. The root cause maps to CWE-497, Exposure of Sensitive System Information to an Unauthorized Control Sphere: the view is deliberately open (AllowAny) so that load balancers and monitoring can poll it, but the serializer it uses was widened to emit the full automation-mesh object graph instead of a minimal status payload. That object graph describes the platform's own control plane - mesh instances (execution, hop, and control nodes), their heartbeats and capacities, instance groups and their membership, and the deployment install UUID - and version fields normalise to the CPE cpe:2.3:a:red_hat:red_hat_ansible_automation_platform_2. None of these fields are secrets, but together they fingerprint the exact release and map the network topology, which is precisely the reconnaissance input an attacker needs to select version-specific exploits and to target the control node. Note the RBAC gating is not defeated: the data is simply serialized through a path that never consults the access controls that would normally protect it.
Know when Django gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Unauthenticated network-reachable AllowAny endpoint (AV:N/AC:L/PR:N/UI:N) leaking only non-secret topology/version metadata gives C:L with no integrity or availability impact.
Primary rating from Vendor (redhat).
CVSS VectorVendor: redhat
DescriptionCVE.org
A flaw was found in the automation-controller API. The unauthenticated health-check endpoint /api/v2/ping/ (ApiV2PingView, AllowAny) over-serializes RBAC-gated automation-mesh data into its anonymous response, exposing the full instance inventory (node hostnames, node types, UUIDs, heartbeats, capacities, and exact versions), all instance-group names and membership, the deployment install UUID, and the active control node. A remote, unauthenticated attacker can use this to map the control plane and fingerprint software versions for targeted attacks. This flaw affects confidentiality only; it does not expose secrets, credentials, or tenant data.
Threat Intelligence Overview
NVD
CVE.org
EPSS
Vulnrichment
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
The package python/cpython from 0 and before 3.6.13, from 3.7.0 and before 3.7.10, from 3.8.0 and before 3.8.8, from 3.9
In Django 1.10.x before 1.10.8 and 1.11.x before 1.11.5, HTML autoescaping was disabled in a portion of the template for
An issue was discovered in Django 3.2 before 3.2.14 and 4.0 before 4.0.6. Rated critical severity (CVSS 9.8), this vulne
Django 3.1.x before 3.1.13 and 3.2.x before 3.2.5 allows QuerySet.order_by SQL injection if order_by is untrusted input
Django before 1.11.27, 2.x before 2.2.9, and 3.x before 3.0.1 allows account takeover. Rated critical severity (CVSS 9.8
An authentication/authorization bypass in the djust Python live-view framework (versions prior to 1.0.7) lets unauthenti
Unauthenticated arbitrary Python module import in djust before 1.0.7 lets any client that can reach the WebSocket or SSE
Django 1.11 before 1.11.29, 2.2 before 2.2.11, and 3.0 before 3.0.4 allows SQL Injection if untrusted data is used as a
Cross-site scripting (XSS) vulnerability in the dismissChangeRelatedObjectPopup function in contrib/admin/static/admin/j
Forged content modification in django-page-cms through 2.0.13 lets unauthenticated remote attackers exploit five CSRF-ex
Cross-site request forgery in djust's Server-Sent-Events transport affects all versions prior to 1.0.7 and allows a cros
Unauthenticated remote attackers can read live Django view and session state and invoke server-side handlers through dju
Exploit-DB