← Übersicht Ansible / Ansible Automation Platform, Red Hat Enterprise Linux

Automation-controller: automation-controller: email notification backend allows ssrf via user-controlled smtp host/port (internal port-scan oracle, smtp password exfil)

CVE-2026-84721

Mittel · CVSS 6.4 Red Hat: Moderate Netzwerk · mit Login Fix verfügbar

Veröffentlicht
23.09.2026
Zuletzt geändert
02.11.2026
EPSS (30 Tage)
0.3 %
CVSS-Vektor
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

Beschreibung

Originaltext der Quelle, nicht übersetzt.

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.

Status beim Hersteller

Red Hat stuft seine Produktlinien ein: 1 betroffen, 1 behoben, 1 nicht betroffen.

Red Hat Ansible Automation Platform 2 BetroffenFix ausstehend ansible-automation-platform-26/controller-rhel9, automation-controller
Red Hat Ansible Automation Platform 2.7 Behoben ansible-automation-platform-27/controller-rhel9 RHSA-2026:71177
Nicht betroffen (1)
Red Hat Ansible Automation Platform 2.7Nicht betroffenverwundbarer Code nicht enthaltenansible-automation-platform-27/aap-must-gather-rhel9, ansible-automation-platform-27/ansible-builder-rhel9, ansible-automation-platform-27/ansible-dev-tools-rhel9, ansible-automation-platform-27/ansible-devspaces-rhel9, ansible-automation-platform-27/controller-rhel9-operator, ansible-automation-platform-27/de-minimal-rhel9, ansible-automation-platform-27/de-supported-rhel9, ansible-automation-platform-27/eda-controller-rhel9, ansible-automation-platform-27/eda-controller-rhel9-operator, ansible-automation-platform-27/eda-controller-ui-rhel9, ansible-automation-platform-27/ee-minimal-rhel9, ansible-automation-platform-27/ee-supported-rhel9, ansible-automation-platform-27/gateway-proxy-rhel9, ansible-automation-platform-27/gateway-rhel9, ansible-automation-platform-27/gateway-rhel9-operator, ansible-automation-platform-27/hub-rhel9, ansible-automation-platform-27/hub-rhel9-operator, ansible-automation-platform-27/hub-web-rhel9, ansible-automation-platform-27/lightspeed-chatbot-rhel9, ansible-automation-platform-27/lightspeed-rhel9, ansible-automation-platform-27/lightspeed-rhel9-operator, ansible-automation-platform-27/mcp-server-rhel9, ansible-automation-platform-27/mcp-tools-rhel9, ansible-automation-platform-27/metrics-service-rhel9, ansible-automation-platform-27/metrics-service-rhel9-operator und 4 weitere

Betroffene Pakete im beobachteten Stack

Red Hat:ansible_automation_platform:2automation-controllerkein Fix bekanntCVE-2026-84721

Empfohlene Prüfung

  1. Feststellen, ob und in welcher Version die betroffenen Pakete in Ihren Systemen, Images und Abhängigkeiten vorkommen.
  2. Wo eine Fix-Version genannt ist: aktualisieren. Wo nicht: Hersteller-Advisory und Referenzen auf Workarounds prüfen.
  3. Erreichbarkeit beachten: Der Angriffsweg (Netzwerk · mit Login) ist aus dem CVSS-Vektor abgeleitet.

Diese Seite sagt nichts darüber, ob Ihre Systeme betroffen sind. Das klärt erst eine Prüfung Ihrer Versionen.