{"id":"CVE-2026-84713","aliases":["EUVD-2026-85610","GHSA-mfxr-44mv-44q4"],"status":"published","title":"Automation-controller: automation-controller: notification.recipients/subject/error lack prevent_search, allowing zero-privilege cross-tenant recovery of notification recipient secrets via filter oracle","description":"A flaw was found in the automation-controller notification\n                  subsystem. Although NotificationTemplate.notification_\n                  configuration is protected from API filtering, its recipient\n                  value is copied in clear text into the unprotected\n                  Notification.recipients field on every send. Because the\n                  credential-types endpoint is listable by any authenticated\n                  user and the API filter backend traverses object relations\n                  without per-hop authorization, a user with no privileges can\n                  use a relational filter as a boolean count-oracle to recover,\n                  character by character and across organizations, the secret\n                  recipient values of other tenants' notifications — including\n                  PagerDuty service keys and Slack/Mattermost/RocketChat/Webhook\n                  bearer-token URLs. This flaw affects confidentiality.","severity":{"version":"3.1","score":6.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","level":"medium","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-11","score":0.00437,"percentile":0.38408,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":false},"cwes":["CWE-639"],"published":"2026-09-23T19:40:26Z","modified":"2026-10-16T12:16:41Z","products":[{"vendor":"red hat","product":"red hat ansible automation platform 2"},{"vendor":"red hat","product":"red hat ansible automation platform 2.7"}],"references":[{"url":"https://access.redhat.com/errata/RHSA-2026:71177","tags":["vendor-advisory","x_refsource_REDHAT"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-84713","tags":["vdb-entry","x_refsource_REDHAT"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2527197","tags":["issue-tracking","x_refsource_REDHAT"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-84713"},{"url":"https://github.com/advisories/GHSA-mfxr-44mv-44q4"}],"sources":{"cve":[{"id":"CVE-2026-84713","title":"Automation-controller: automation-controller: notification.recipients/subject/error lack prevent_search, allowing zero-privilege cross-tenant recovery of notification recipient secrets via filter oracle","description":"A flaw was found in the automation-controller notification\n                  subsystem. Although NotificationTemplate.notification_\n                  configuration is protected from API filtering, its recipient\n                  value is copied in clear text into the unprotected\n                  Notification.recipients field on every send. Because the\n                  credential-types endpoint is listable by any authenticated\n                  user and the API filter backend traverses object relations\n                  without per-hop authorization, a user with no privileges can\n                  use a relational filter as a boolean count-oracle to recover,\n                  character by character and across organizations, the secret\n                  recipient values of other tenants' notifications — including\n                  PagerDuty service keys and Slack/Mattermost/RocketChat/Webhook\n                  bearer-token URLs. This flaw affects confidentiality.","status":"published","published":"2026-09-23T19:40:26.061Z","modified":"2026-10-16T11:55:09.585Z","cvss":[{"version":"3.1","score":6.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","level":"medium","assessor":"cna"}],"cwes":["CWE-639"],"updated_at":"2026-11-02T14:20:08.391556Z"}],"euvd":[{"id":"EUVD-2026-85610","description":"A flaw was found in the automation-controller notification\n                  subsystem. Although NotificationTemplate.notification_\n                  configuration is protected from API filtering, its recipient\n                  value is copied in clear text into the unprotected\n                  Notification.recipients field on every send. Because the\n                  credential-types endpoint is listable by any authenticated\n                  user and the API filter backend traverses object relations\n                  without per-hop authorization, a user with no privileges can\n                  use a relational filter as a boolean count-oracle to recover,\n                  character by character and across organizations, the secret\n                  recipient values of other tenants' notifications — including\n                  PagerDuty service keys and Slack/Mattermost/RocketChat/Webhook\n                  bearer-token URLs. This flaw affects confidentiality.","status":"published","published":"2026-09-23T19:40:26Z","modified":"2026-10-16T11:55:09Z","cvss":[{"version":"3.1","score":6.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","level":"medium"}],"updated_at":"2026-11-02T17:00:06.126239Z"}],"ghsa":[{"id":"GHSA-mfxr-44mv-44q4","title":"A flaw was found in the automation-controller notification\n                  subsystem. Although...","description":"A flaw was found in the automation-controller notification\n                  subsystem. Although NotificationTemplate.notification_\n                  configuration is protected from API filtering, its recipient\n                  value is copied in clear text into the unprotected\n                  Notification.recipients field on every send. Because the\n                  credential-types endpoint is listable by any authenticated\n                  user and the API filter backend traverses object relations\n                  without per-hop authorization, a user with no privileges can\n                  use a relational filter as a boolean count-oracle to recover,\n                  character by character and across organizations, the secret\n                  recipient values of other tenants' notifications — including\n                  PagerDuty service keys and Slack/Mattermost/RocketChat/Webhook\n                  bearer-token URLs. This flaw affects confidentiality.","status":"published","published":"2026-09-23T21:30:57Z","modified":"2026-09-24T09:31:50Z","cvss":[{"version":"3.1","score":6.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","level":"medium"}],"cwes":["CWE-639"],"updated_at":"2026-11-02T15:12:22.2852Z"}],"nvd":[{"id":"CVE-2026-84713","description":"A flaw was found in the automation-controller notification\n                  subsystem. Although NotificationTemplate.notification_\n                  configuration is protected from API filtering, its recipient\n                  value is copied in clear text into the unprotected\n                  Notification.recipients field on every send. Because the\n                  credential-types endpoint is listable by any authenticated\n                  user and the API filter backend traverses object relations\n                  without per-hop authorization, a user with no privileges can\n                  use a relational filter as a boolean count-oracle to recover,\n                  character by character and across organizations, the secret\n                  recipient values of other tenants' notifications — including\n                  PagerDuty service keys and Slack/Mattermost/RocketChat/Webhook\n                  bearer-token URLs. This flaw affects confidentiality.","status":"published","published":"2026-09-23T20:17:17.95Z","modified":"2026-10-16T12:16:41.33Z","cvss":[{"version":"3.1","score":6.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","level":"medium","assessor":"secondary"}],"cwes":["CWE-639"],"updated_at":"2026-11-02T14:12:51.036099Z"}]}}