VulnerabilityPublished 23 Sep 2026Updated 2 Nov 2026

CVE-2026-84721: Red Hat Ansible Automation Platform 2.7 · Server-Side Request Forgery

Affects Red Hat Ansible Automation Platform 2.7Source CVE Database V5

Compare

Not known to be exploited · CVSS 6.4 Medium.

Data as of 7 Nov 2026, 11:40 UTC

CVSS 3.1 base score

6.4Medium

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	6.4

EPSS: 0.2% chance of exploitation in 30 days – higher than 22% 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:C/C:L/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Changed
Confidentiality: Low
Integrity: Low
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: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
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: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on 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.7ansible-automation-platform-27/controller-rhel9	Affected–	Fixed in–
Red Hat Ansible Automation Platform 2ansible-automation-platform-26/controller-rhel9	Affected–	Fixed in–
Red Hat Ansible Automation Platform 2automation-controller	Affected–	Fixed in–

AI-suggested

Red Hat currently does not provide an official fix or mitigation that meets their product security criteria for this issue. The vendor advisory states that mitigation options are either unavailable or not suitable for widespread deployment or stability. Users should monitor Red Hat's advisory page for updates. Until a fix is available, restricting notification-admin permissions to trusted users and avoiding the use of shared templates with stored SMTP credentials may reduce risk.

Description

CVE-2026-84721 is a server-side request forgery (SSRF) vulnerability in the email notification backend of Red Hat Ansible Automation Platform 2.7. It allows an authenticated user with notification-admin permission to specify arbitrary internal SMTP hosts and ports in notification templates, causing the controller to open raw TCP connections to internal or reserved network addresses. This can be used as a port-scanning oracle within the cluster network and may lead to SMTP credential exfiltration if stored passwords are used in shared templates.

Impact

An authenticated user with notification-admin permissions can exploit this SSRF vulnerability to perform internal network reconnaissance via port scanning within the cluster network, potentially exposing sensitive infrastructure details. Furthermore, if SMTP credentials are stored in shared notification templates, these credentials can be exfiltrated to attacker-controlled servers, leading to credential compromise. The CVSS score of 6.4 reflects a medium severity impact with confidentiality and integrity impacts but no availability impact.

Summary

This vulnerability arises because the email notification backend in Red Hat Ansible Automation Platform 2.7 does not validate user-supplied SMTP host and port values against internal, loopback, link-local, or reserved IP addresses before opening TCP connections. An attacker with organization notification-admin privileges can create or modify email notification templates to point to arbitrary internal addresses and trigger connection attempts. The connection results are reflected back, enabling internal port scanning of the control-plane cluster network, including the Kubernetes API. Additionally, if a shared notification template contains stored SMTP credentials, these can be sent to an attacker-controlled server, leading to credential exposure. The flaw is specific to the email backend; other notification backends like HTTP have been hardened. Red Hat notes that proper validation should be implemented across all notification backends and currently exists only in the 2.7 branch.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 3 Nov 2026, 11:43 UTC

Technical details

References

Community reviews

Related threats