CVE-2026-109131: Ansible-ui: ansible-ui: stored xss via unsafe javascript url scheme in hub collection module documentation (formatparturl)
Rate Moderate - exploitation requires an authenticated user with the collection-namespace owner role to store the payload (roleless upload is rejected), and a separate authenticated viewer must actively activate the crafted link (no execution on page load); the build CSP does not block the script-executing scheme. Component mapping confirmed via newcli: Platform UI assets ship in automation-gateway (2.5 RPM), automation-platform-ui (2.6 RPM), and the gateway-rhel9 container (2.6 and 2.7); standalone ansible-hub-ui uses a different, non-reproduced renderer. Source flaw component = upstream ansible-ui (frontend/hub).
Other sources
The Hub collection module documentation renderer in the unified Ansible Automation Platform UI (built from upstream ansible-ui, frontend/hub) renders a documentation URL part (formatPartURL in DocumentationParsers.tsx) as a link without restricting the URL protocol/scheme. A collection whose documentation contains a link using a script-executing URL scheme can therefore cause script to run in the same origin as the Hub UI when another authenticated user views and activates that link in the collection documentation page. This is a stored cross-site scripting issue in shipped Platform UI code (present in the AAP 2.6 and 2.7 release branches).
— MITRE
Affected Software
Event History
Frequently Asked Questions
Who can introduce the malicious content, and who is exposed to it?
An authenticated user with the collection-namespace owner role can store the payload in collection documentation; uploads without that role are rejected. A separate authenticated user is exposed only if they view the affected collection documentation and activate the crafted link.
Does simply opening the documentation trigger the XSS?
No. The payload does not execute on page load; the viewer must actively click or otherwise activate the crafted documentation link.
Which shipped components are confirmed affected?
The affected Platform UI assets ship in automation-gateway 2.5 RPM, automation-platform-ui 2.6 RPM, and the gateway-rhel9 container in 2.6 and 2.7. Standalone ansible-hub-ui uses a different renderer and was not reproduced as affected.
What limits exploitation if remediation cannot be applied immediately?
Restrict collection-namespace owner access to trusted users and review collection documentation submitted by namespace owners for script-executing URL schemes. Users should avoid activating suspicious links in Hub collection documentation.