Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as org notification-admin
-
DeliverySet SMTP host/port to internal target in email template
-
ExploitTrigger test notification
-
ExecutionController opens raw TCP connection
-
PersistRead reflected connection error as port oracle
-
ImpactMap cluster services / exfil stored SMTP credential
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V4 - API and Web Service URL allowlisting, SSRF prevention
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Credential Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires an authenticated user with organization notification-admin permission on the automation-controller - this is a privileged role, so it is not remotely reachable by anonymous users. The attacker must be able to create or modify an email notification template and trigger a test send. Exploitation depends on the controller's task network having reachable internal targets (loopback, link-local, reserved ranges, or the in-cluster Kubernetes API) - most impactful in the standard OpenShift/Kubernetes cluster deployment where the control-plane network hosts sensitive services. The credential-exfiltration escalation additionally requires that a shared organization email template already stores an SMTP password. |
| Impact | This is a moderate, credibly-real SSRF (CWE-918) but not an emergency. The vendor CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N = 6.4) is internally consistent with the description: network-reachable, low complexity, but gated behind PR:L - the attacker must already hold organization notification-admin permission, a privileged role. The S:C (scope change) is justified because the SSRF pivots out of the application into the control-plane cluster network and the in-cluster Kubernetes API. No EPSS score, no CISA KEV listing, and no public POC were provided, so the exploitation signal is entirely theoretical: no public exploit identified at time of analysis. The primary impact is an information-only internal port-scan oracle (three-state: open/closed/filtered), which is reconnaissance rather than direct compromise - consistent with C:L/I:L/A:N. The secondary SMTP-credential-exfiltration path is more serious but conditional: it only fires when a shared organization template already stores an SMTP password, which the vendor evidently reflected by keeping C:L rather than C:H. Net: a genuine defense-in-depth issue for AAP operators, not a mass-exploitation priority. The main limiting factor is the privileged-role prerequisite; absent that, this is not reachable. |
| Exploit ScenarioDerived | An authenticated user holding organization notification-admin permission in Ansible Automation Platform creates or edits an email notification template, sets the SMTP host/port to an internal target (e.g., the in-cluster Kubernetes API or a loopback/link-local service), and triggers a test send. The controller task process opens a raw TCP connection and reflects the connection result back through the notification record, giving an open/closed/filtered oracle for mapping control-plane services; if a shared template already stores an SMTP password, redirecting the host also leaks that credential to the attacker's server. No public POC is referenced. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 23, 2026
Server-side request forgery in Red Hat Ansible Automation Platform 2's automation-controller email notification backend lets an authenticated user holding organization notification-admin permission point an email notification template's SMTP host and port at arbitrary internal, loopback, link-local or reserved addresses; the controller task process then opens a raw TCP connection to that target when the notification test is triggered. Because the resulting connection error is surfaced through the notification record, an attacker gains a three-state internal port-scan oracle (open, closed, filtered) over the control-plane cluster network, including the in-cluster Kubernetes API, and if a shared organization template stores an SMTP password, redirecting the host can leak that credential to an attacker-controlled server. Impact is moderate (vendor CVSS 6.4, CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N) and requires a privileged, already-authenticated role rather than anonymous access; no public exploit code has been identified at time of analysis and CISA KEV does not list this CVE.
RemediationAI
No vendor-released patch is identified in the available data at time of analysis; consult the Red Hat CVE page (https://access.redhat.com/security/cve/CVE-2026-84721) and Bugzilla 2527220 (https://bugzilla.redhat.com/show_bug.cgi?id=2527220) for errata and any fixed automation-controller release before assuming remediation is available. Until then, restrict the organization notification-admin role to the smallest set of trusted operators, since the entire exploit path depends on that privileged permission to create or modify an email notification template and trigger a test send - this is the cheapest and most direct mitigation, with the trade-off that day-to-day notification management must be centralized. Do not store SMTP passwords on shared organization-level templates; use per-user or per-credential SMTP authentication so that a redirected host cannot harvest a reusable secret, accepting the added credential-management overhead. Enforce egress network controls on the controller task pods (Kubernetes NetworkPolicy or equivalent firewall rules) that deny outbound connections to loopback, link-local, reserved and the in-cluster Kubernetes API and service CIDR ranges, permitting only an explicit allowlist of approved SMTP relays - the trade-off is that overly broad egress blocking can break legitimate mail delivery and any other outbound integrations the controller relies on, so build the allowlist iteratively in a test namespace. Add audit and alerting on notification template creation or modification events that change SMTP host or port, and treat any notification record showing connection errors to internal addresses as an exploitation indicator. Finally, review whether the automation-controller task network can reach sensitive control-plane services at all; segmenting that network reduces this SSRF from a reconnaissance primitive against the Kubernetes API to a low-value connectivity probe.
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The flaw is a classic server-side request forgery (CWE-918) in the automation-controller component of Ansible Automation Platform 2, specifically in the email notification backend. The backend takes the user-supplied SMTP host and port from a notification template and hands them to the underlying SMTP client without validating that the resolved target is not an internal, loopback, link-local or reserved address. There is no allowlist of permitted mail relays and no post-resolution address filtering, so the SMTP client will happily dial whatever IP the template names. Two properties make this more than a trivial duplicate of ordinary SSRF: first, the SMTP client's connection result (success, refused, timeout) is propagated back into the notification record, turning the error channel into a stateful port-scan oracle that distinguishes open, closed and filtered ports from a privileged position inside the cluster network; second, the CVSS scope is marked Changed (S:C) because the compromised component's behavior reaches resources outside its own security scope - the control-plane cluster network and the in-cluster Kubernetes API. The credential-disclosure variant arises because SMTP authentication material stored on a shared organization template is sent to whatever host the template points at, so a redirected host receives the stored password. CPE data identifies the affected product as cpe:2.3:a:red_hat:red_hat_ansible_automation_platform_2 with wildcarded version components, meaning the vendor has not narrowed the affected version range in the CPE at the time of analysis.
Know when Kubernetes gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
PR:L for the required notification-admin role; S:C because the SSRF pivots into the cluster/K8s API network; C:L/I:L for the port-scan oracle and conditional credential leak, A:N as no availability impact.
Primary rating from Vendor (redhat).
CVSS VectorVendor: redhat
DescriptionCVE.org
A server-side request forgery flaw was found in the Ansible Automation Platform automation-controller email notification backend. The email backend passes the user-supplied SMTP host and port from a notification template directly to the SMTP client without validating that the target is not an internal, loopback, link-local, or reserved address. An authenticated user with organization notification-admin permission can create or modify an email notification template pointing at an arbitrary internal address, trigger a test, and have the controller task process open a raw TCP connection to that address. The resulting connection error is reflected back through the notification record, providing a three-state internal port-scan oracle (open, closed, filtered) over the control-plane's cluster network, including the in-cluster Kubernetes API. When a shared organization template holds a stored SMTP password, redirecting the host can also cause that credential to be transmitted to an attacker-controlled server.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Server-Side Request Forgery exploits applications that fetch remote resources based on user-supplied URLs.
Affected Products (CPE)CVE.org
More in Kubernetes
View allA critical vulnerability in Kubernetes ingress-nginx controller allows unauthenticated attackers with pod network access
Credential-harvesting malware compromised 84 versions of 42 TanStack npm packages on 2026-05-11 via chained GitHub Actio
Kubernetes ingress-nginx contains a configuration injection vulnerability via the mirror-target and mirror-host Ingress
A security issue was discovered in ingress-nginx https://github.com/kubernetes/ingress-nginx where the `auth-url` Ingres
A security issue was discovered in ingress-nginx https://github.com/kubernetes/ingress-nginx where the `auth-tls-match-c
Kubernetes API server in all versions allow an attacker who is able to create a ClusterIP service and set the spec.exter
A security issue was discovered in Kubernetes where a user that can create pods on Windows nodes may be able to escalate
Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. Rated critical severity (CVSS 9.9), this vulne
Unauthenticated remote attackers can trigger complete database overwrites, server-side file reads, and SSRF attacks agai
The Kubernetes integration in GitLab Enterprise Edition 11.x before 11.2.8, 11.3.x before 11.3.9, and 11.4.x before 11.4
Fluentd configuration injection in the kube-logging Logging operator before 6.6.0 allows a namespace-scoped user who can
Kyverno Kubernetes policy engine prior to 1.x has a privilege escalation vulnerability (CVSS 9.9) allowing policy bypass
EUVD-2026-85615
GHSA-pm79-7whg-hpfr
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB