GPU VulnDB

Database/Control plane, storage & DevOps

ansible-core: ansible-galaxy role name path traversal writes files outside the roles directory

CVSS 8.1CVE-2026-105929Control plane, storage & DevOpscurated

Impact

ansible-galaxy builds a role's install path from the role name in meta/requirements.yml without checking that the path stays inside the roles directory. A name containing "../", or an absolute name, writes attacker-supplied files elsewhere. With --force it can also delete and replace an existing directory outside that path. Transitive dependencies are processed too, so a role that looks harmless can pull in a malicious one. Fleet provisioning hosts often run ansible-galaxy as a privileged deploy user, so this can overwrite playbooks, inventories or other files that later run across every GPU node. The impact is limited to what the invoking user can write.

Who can reach it

A malicious role publisher, or anyone who can influence a role dependency. The operator must install that content with ansible-galaxy. No authentication to the operator's systems is needed.

What to do

Update ansible-core on control and CI hosts to the fixed build in the Red Hat advisory. The record does not give a version. This is a package update on control nodes only; managed nodes need nothing. Until then, pin roles to trusted sources and versions, avoid --force, and do not run ansible-galaxy as root.

References

Related entries

All Control plane, storage & DevOps entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.