CVE-2026-84712

Automation-controller: automation-controller: unauthenticated /api/v2/ping/ discloses automation-mesh instance topology and instance-group membership

  • Medium 5.3

Description

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.

Key facts

Published
23 Sep 2026
Last changed
6 Nov 2026
Assigned by
redhat
EPSS
0.388% likely to be exploited in the next 30 days, higher than 33.41% of CVEs (scores for 17 Nov 2026)
SSVC (CISA)
Exploitation: none; Automatable: yes; Technical impact: partial

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 5.3CVSS 3.1, Mediumfrom the CNA (redhat)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

What to do

  • There is no configuration option that trims the data returned by the unauthenticated /api/v2/ping/ endpoint (also reachable as /api/controller/v2/ping/). Exposure can be reduced by restricting network access to the automation-controller API so that only trusted networks and health probes can reach it: block or restrict external access to the /api/v2/ping/ and /api/controller/v2/ping/ routes at the reverse proxy, load balancer, or firewall, and front health checks with an infrastructure-level probe that does not proxy the /ping/ endpoint to untrusted clients. The definitive fix is to update to a version of automation-controller that no longer serializes instance, instance-group, install UUID, and active-node data in the unauthenticated response.CNA workaround statement

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
Red HatRed Hat Ansible Automation Platform 2.5 for RHEL 8
  • Default status: affected
  • 0:4.6.33-1.el8ap up to but excluding * (unaffected)
Red HatRed Hat Ansible Automation Platform 2.5 for RHEL 8
  • Default status: affected
  • 0:4.6.33-1.el8ap up to but excluding * (unaffected)
Red HatRed Hat Ansible Automation Platform 2.5 for RHEL 9
  • Default status: affected
  • 0:4.6.33-1.el9ap up to but excluding * (unaffected)
Red HatRed Hat Ansible Automation Platform 2.5 for RHEL 9
  • Default status: affected
  • 0:4.6.33-1.el9ap up to but excluding * (unaffected)
Red HatRed Hat Ansible Automation Platform 2.6 for RHEL 9
  • Default status: affected
  • 0:4.7.17-1.el9ap up to but excluding * (unaffected)
Red HatRed Hat Ansible Automation Platform 2.6 for RHEL 9
  • Default status: affected
  • 0:4.7.17-1.el9ap up to but excluding * (unaffected)
Red HatRed Hat Ansible Automation Platform 2.6
  • Default status: affected
  • 1789673739 up to but excluding * (unaffected)
Red HatRed Hat Ansible Automation Platform 2.7
  • Default status: affected
  • 1789580684 up to but excluding * (unaffected)

Timeline

  1. 2 Sep 2026 Reported to Red Hat.
  2. 23 Sep 2026 Made public.
  3. 23 Sep 2026 Published

Weakness

References