Quick answers
- Is CVE-2026-84712 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-84712 being exploited in the wild.
- How severe is CVE-2026-84712?
- Medium severity, with a CVSS score of 5.3, published 23 September 2026.
- Which products and versions are affected?
- Red Hat Ansible Automation Platform not specified.
- Is there a fix for CVE-2026-84712?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-84712 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-84712?
- Check whether you run Red Hat Ansible Automation Platform at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The /api/v2/ping/ endpoint in Ansible Automation Controller over-serializes RBAC-protected automation-mesh data in its unauthenticated response, disclosing full instance inventory (hostnames, node types, UUIDs, heartbeats, capacities, versions), instance-group names and membership, deployment install UUID, and active control node information. No authentication is required; the attack is a simple HTTP GET. The vulnerability exposes confidential infrastructure topology but not secrets or credentials.
Affected products
- Red Hat Ansible Automation Platform not specified
Timeline
- 2026-09-23: disclosed