# CVE-2026-84713: Information disclosure in Red Hat Ansible Automation Platform 2

> Zero-privilege users can recover other tenants' notification secrets via a filter oracle in the automation-controller notification subsystem.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Sep 2026
- **Updated:** 16 Oct 2026
- **Also known as:** GHSA-mfxr-44mv-44q4

## What is CVE-2026-84713?

CVE-2026-84713 is a medium-severity vulnerability in Red Hat Ansible Automation Platform 2, published on 23 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-84713?


## How do I fix CVE-2026-84713?

No fix has been published for CVE-2026-84713 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-84713 being exploited?

There is no known exploitation of CVE-2026-84713 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-84713 and fix it if it is affected.

What it is: CVE-2026-84713 is a medium-severity vulnerability in Red Hat Ansible Automation Platform 2, published on 23 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-84713 in the wild and no public exploit code.

Affected product: Red Hat Ansible Automation Platform 2. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-84713/ (Markdown: https://insights.sbomify.com/CVE-2026-84713/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-84713
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-84713
- OSV: https://osv.dev/vulnerability/CVE-2026-84713

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-84713/
Summaries are generated and may contain mistakes; the official description above is the record.