CVE-2026-84713

Description

A flaw was found in the automation-controller notification subsystem. Although NotificationTemplate.notification_ configuration is protected from API filtering, its recipient value is copied in clear text into the unprotected Notification.recipients field on every send. Because the credential-types endpoint is listable by any authenticated user and the API filter backend traverses object relations without per-hop authorization, a user with no privileges can use a relational filter as a boolean count-oracle to recover, character by character and across organizations, the secret recipient values of other tenants' notifications — including PagerDuty service keys and Slack/Mattermost/RocketChat/Webhook bearer-token URLs. This flaw affects confidentiality.

Statement

A MODERATE severity information disclosure flaw was found in the automation-controller component of Red Hat Ansible Automation Platform. The NotificationTemplate notification_configuration field is protected from API filtering, but each time a notification is sent the recipient value is copied in clear text into the unprotected Notification.recipients field. Because the credential-types API endpoint is listable by any authenticated user regardless of roles, and the API filter backend traverses object relations without per-hop authorization, an authenticated attacker with low privileges and no organization membership can use a relational filter as a boolean count-oracle to recover, one character at a time and across organizations, the secret recipient values stored in other tenants' notifications — including PagerDuty Events-API service keys and Mattermost, RocketChat, and generic Webhook incoming-webhook URLs that embed bearer tokens — as well as each notification's subject and error text. Only confidentiality is affected (CVSS 6.5, CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N), which matches the upstream severity. Red Hat Ansible Automation Platform 2.6 and 2.7 are affected and a fix is being pursued through the delegated process; for the 2.4 and 2.5 streams no fix is planned, leaving the residual risk of cross-tenant disclosure of live notification credentials there.

Mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

Common Vulnerability Scoring System (CVSS) Score Details

Info alert:Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score6.5N/A6.5
Attack VectorNetworkN/ANetwork
Attack ComplexityLowN/ALow
Privileges RequiredLowN/ALow
User InteractionNoneN/ANone
ScopeUnchangedN/AUnchanged
ConfidentialityHighN/AHigh
Integrity ImpactNoneN/ANone
Availability ImpactNoneN/ANone

Vector

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

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

Understanding the Weakness (CWE)

Access Control

Technical Impact: Bypass Protection Mechanism

Access control checks for specific user data or functionality can be bypassed.

Access Control

Technical Impact: Gain Privileges or Assume Identity

Horizontal escalation of privilege is possible (one user can view/modify information of another user).

Access Control

Technical Impact: Gain Privileges or Assume Identity

Vertical escalation of privilege is possible if the user-controlled key is actually a flag that indicates administrator status, allowing the attacker to gain administrative access.

Frequently Asked Questions

Want to get errata notifications? Sign up here.