CVE-2026-84712 Red Hat CVE debrief

Who should care

Defenders managing Red Hat Ansible Automation Platform deployments, especially those using automation-controller, should assess their exposure and prioritize patching or mitigating the flaw to prevent potential targeted attacks.

Why it matters

CVE-2026-84712 allows unauthenticated access to sensitive automation-mesh instance topology and instance-group membership information in Red Hat Ansible Automation Platform, affecting confidentiality and potentially aiding targeted attacks.

• Defenders must verify exposure of automation-controller deployments to the /api/v2/ping/ endpoint.
• Exposed automation-mesh topology and instance-group membership could be used for targeted attacks.
• Defenders should assess the impact on their automation-controller deployments and prioritize patching or mitigation.
• Verification of affected versions and application of patches or updates is necessary.

Technical summary

The automation-controller API has a flaw allowing unauthenticated access to sensitive automation-mesh instance topology and instance-group membership information via the /api/v2/ping/ endpoint. Exposed data includes node hostnames, types, UUIDs, heartbeats, capacities, versions, instance-group names, membership details, the deployment install UUID, and the active control node. This flaw affects confidentiality and could be used for targeted attacks by mapping the control plane and fingerprinting software versions. Defenders should prioritize verifying exposure and assessing the impact on their automation-controller deployments, especially those using Red Hat Ansible Automation Platform.

Defensive priority

Defenders should prioritize verifying exposure and assessing the impact on their automation-controller deployments, especially those using Red Hat Ansible Automation Platform.

Recommended defensive actions

• Verify the automation-controller deployment for exposure to the /api/v2/ping/ endpoint.
• Assess the impact of exposed automation-mesh instance topology and instance-group membership.
• Apply patches or updates provided by Red Hat for affected versions.
• Monitor for potential targeted attacks using the exposed information.
• Review compensating controls for exposed systems while remediation is scheduled and verified.
• Check relevant monitoring, detection, and logs for exposed assets that need extra review.
• Track exceptions, retest remediated assets, and close the item only after evidence is documented.

Evidence notes

The CVE record and source item provide details on the flaw, its impact, and affected products. Red Hat has provided errata for affected versions. Defenders should verify exposure of automation-controller deployments to the /api/v2/ping/ endpoint and assess the impact on their automation-controller deployments. Verification of affected versions and application of patches or updates is necessary. The flaw allows unauthenticated access to sensitive automation-mesh instance topology and instance-group membership information.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.