{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-84716 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-84716 is a medium-severity vulnerability in Red Hat Ansible Automation Platform 2.5 for RHEL 8, published on 23 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-84716 and fix it if it is affected.\n\nWhat it is: CVE-2026-84716 is a medium-severity vulnerability in Red Hat Ansible Automation Platform 2.5 for RHEL 8, published on 23 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-84716 in the wild and no public exploit code.\n\nAffected product: Red Hat Ansible Automation Platform 2.5 for RHEL 8. 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-84716/ (Markdown: https://insights.sbomify.com/CVE-2026-84716/index.md)","id":"CVE-2026-84716","markdown":"https://insights.sbomify.com/CVE-2026-84716/index.md","name":"CVE-2026-84716","record":{"aliases":["GHSA-hcpg-prc4-w26w"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["security_bypass","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Ansible Automation Platform","requires_auth":"high_privilege","summary":"Administrators can obtain long-lived, non-revocable mesh certificates for impersonated hostnames, enabling TLS interception of control nodes in managed deployments.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[],"cvss":{"score":6.6,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-266","name":"Incorrect Privilege Assignment"}],"description":"A flaw was found in the automation-controller instance\n                  install-bundle endpoint. When a System Administrator downloads\n                  an execution/hop node's install bundle, the controller signs an\n                  X.509 certificate with the receptor mesh certificate authority\n                  in which the Common Name, DNS subject-alternative-name, and\n                  receptor node-id are taken verbatim from the caller-chosen\n                  instance hostname, with a hard-coded ten-year validity, a random\n                  serial, and no issuance log or revocation list. Because the\n                  hostname charset validator is case-insensitive while the\n                  uniqueness validator is case-sensitive, an administrator can\n                  register a case variant of an existing control node's hostname\n                  and obtain a mesh-CA-signed certificate that TLS peers, which\n                  match hostnames case-insensitively, accept as that control node.\n                  In managed/hosted deployments — where the customer holds\n                  controller superuser but the platform operator runs the mesh —\n                  this yields a long-lived, non-revocable mesh peer credential and,\n                  with an on-path position, TLS impersonation or interception of\n                  control/hybrid mesh nodes. It does not grant direct remote code\n                  execution, because receptor work submission is gated by a\n                  separate signing key not included in the bundle.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Security feature bypass in Red Hat Ansible Automation Platform 2.5 for RHEL 8","id":"CVE-2026-84716","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"Information disclosure in Red Hat Ansible Automation Platform 2.5 for RHEL 8","id":"CVE-2026-84717"},"packages":[],"prev":{"headline":"FeatherPanel before 1.3.7.10 Privilege Escalation via Subuser Permission Update","id":"CVE-2026-84715"},"products":["Red Hat Ansible Automation Platform 2.5 for RHEL 8","Red Hat Ansible Automation Platform 2.5 for RHEL 9","Red Hat Ansible Automation Platform 2.6","Red Hat Ansible Automation Platform 2.6 for RHEL 9","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":"Administrators can obtain long-lived, non-revocable mesh certificates for impersonated hostnames, enabling TLS interception of control nodes in managed deployments.","url":"https://insights.sbomify.com/CVE-2026-84716/"}