{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-84713 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-84713 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-84713 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2026-84713 in the wild and no public exploit code.\n\nAffected product: Red Hat Ansible Automation Platform 2. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-84713/ (Markdown: https://insights.sbomify.com/CVE-2026-84713/index.md)","id":"CVE-2026-84713","markdown":"https://insights.sbomify.com/CVE-2026-84713/index.md","name":"CVE-2026-84713","record":{"aliases":["GHSA-mfxr-44mv-44q4"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Ansible Automation Platform","requires_auth":"low_privilege","summary":"Zero-privilege users can recover other tenants' notification secrets via a filter oracle in the automation-controller notification subsystem.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-639","name":"Authorization Bypass Through User-Controlled Key"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Information disclosure in Red Hat Ansible Automation Platform 2","id":"CVE-2026-84713","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"Code injection in Red Hat Ansible Automation Platform 2.5 for RHEL 8","id":"CVE-2026-84714"},"packages":[],"prev":{"headline":"Information disclosure in Red Hat Ansible Automation Platform 2.5 for RHEL 8","id":"CVE-2026-84712"},"products":["Red Hat Ansible Automation Platform 2","Red Hat Ansible Automation Platform 2.7"],"published":"2026-09-23","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-16","vendors":["Red Hat"]},"summary":"Zero-privilege users can recover other tenants' notification secrets via a filter oracle in the automation-controller notification subsystem.","url":"https://insights.sbomify.com/CVE-2026-84713/"}