Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By redhat

  2. · 21 days later

    Published

  3. · 44 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-84712, by who scored it
Scored byCVSSScoreVector
redhatCNA (assigner)3.1Medium5.3CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
NVDNVD · Awaiting Analysis3.1Medium5.3CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
EPSS (exploitation in 30 days)
0.39% · top 67% of all CVEs (18 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: yes · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.3.

Affected products

What to do

Workaround: 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.

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-84712 badge
[![CVE-2026-84712](https://cveledger.app/badge/CVE-2026-84712.svg)](https://cveledger.app/cve/CVE-2026-84712)

Record last updated .