VulnerabilityPublished 23 Sep 2026Updated 6 Nov 2026

CVE-2026-84712: Red Hat Ansible Automation Platform 2.5 for RHEL 8 · Exposure of Sensitive System Information to an Unauthorized Control Sphere

Affects Red Hat Ansible Automation Platform 2.5 for RHEL 8Source CVE Database V5

Compare

Not known to be exploited · CVSS 5.3 Medium.

Data as of 7 Nov 2026, 11:40 UTC

CVSS 3.1 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CNA (redhat)	CVSS 3.1	5.3

EPSS: 0.3% chance of exploitation in 30 days – higher than 33% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 23 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 7 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Red Hat Ansible Automation Platform 2.5 for RHEL 8automation-controller	Affected–	Fixed in–
Red Hat Ansible Automation Platform 2.5 for RHEL 9automation-controller	Affected–	Fixed in–
Red Hat Ansible Automation Platform 2.6 for RHEL 9automation-controller	Affected–	Fixed in–
Red Hat Ansible Automation Platform 2.6ansible-automation-platform-26/controller-rhel9	Affected–	Fixed in–
Red Hat Ansible Automation Platform 2.7ansible-automation-platform-27/controller-rhel9	Affected–	Fixed in–

AI-suggested

There is no configuration option to reduce the data returned by the unauthenticated /api/v2/ping/ endpoint. Operators should restrict network access to the automation-controller API so that only trusted networks and health probes can reach it. This includes blocking or restricting external access to the /api/v2/ping/ and /api/controller/v2/ping/ routes at the reverse proxy, load balancer, or firewall. Health checks should be fronted with infrastructure-level probes that do 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.

Description

CVE-2026-84712 is a vulnerability in Red Hat Ansible Automation Platform 2.5 for RHEL 8 where the unauthenticated health-check endpoint /api/v2/ping/ over-serializes sensitive automation-mesh data. This exposure allows remote attackers to obtain detailed instance inventory and deployment information, potentially aiding targeted attacks. The flaw affects confidentiality but does not expose secrets, credentials, or tenant data. There is no configuration workaround to trim the data returned by this endpoint. Operators should restrict network access to the API and front health checks with infrastructure probes that do not proxy the /ping/ endpoint. The definitive fix is to update to a version that stops serializing sensitive data in the unauthenticated response.

Impact

The vulnerability exposes sensitive system information related to the automation-mesh topology and deployment details to unauthenticated remote attackers. This information disclosure affects confidentiality only and does not compromise secrets, credentials, or tenant data. Attackers can use the exposed data to map the control plane and fingerprint software versions, potentially facilitating targeted attacks against the system.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 6 Nov 2026, 12:01 UTC

Technical details

References

Community reviews

Related threats