VulnerabilityPublished 23 Sep 2026Updated 16 Oct 2026

CVE-2026-84713: Red Hat Ansible Automation Platform 2.7 · Insecure Direct Object Reference

Affects Red Hat Ansible Automation Platform 2.7Source CVE Database V5

Compare

Not known to be exploited · CVSS 6.5 Medium.

Data as of 5 Nov 2026, 23:24 UTC

CVSS 3.1 base score

6.5Medium

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

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

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: High
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: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
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: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
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 5 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 HatRed Hat Ansible Automation Platform 2.7	Affected–	Fixed in–
Red HatRed Hat Ansible Automation Platform 2	Affected–	Fixed in–

AI-suggested

An official fix is available as per the Red Hat advisory RHSA-2026:71177. Users of Red Hat Ansible Automation Platform 2.7 should apply the update provided by Red Hat to remediate this vulnerability. Refer to the vendor advisory for upgrade instructions and ensure all previously released errata are applied before updating.

Description

CVE-2026-84713 is a vulnerability in Red Hat Ansible Automation Platform 2.7's automation-controller notification subsystem. It allows an authenticated user with no privileges to recover secret recipient values from other tenants' notifications by exploiting insufficient authorization checks in API filtering. This leads to unauthorized disclosure of sensitive information such as PagerDuty service keys and webhook bearer tokens. The vulnerability affects confidentiality but does not impact integrity or availability.

Impact

Confidentiality is impacted as secret recipient values, including PagerDuty service keys and Slack/Mattermost/RocketChat/Webhook bearer-token URLs, can be disclosed to unauthorized users. There is no impact on integrity or availability.

Summary

The vulnerability exists because NotificationTemplate.notification_configuration is protected from API filtering, but its recipient value is copied in clear text into the unprotected Notification.recipients field on every send. The credential-types endpoint is listable by any authenticated user, and the API filter backend traverses object relations without per-hop authorization. This allows a low-privileged user to use a relational filter as a boolean count-oracle to recover secret recipient values character by character across organizations, exposing sensitive notification credentials.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 16 Oct 2026, 20:00 UTC

Technical details

References

Community reviews

Related threats