GPU VulnDB

Database/Control plane, storage & DevOps

ansible-core: collection metadata name path traversal deletes and overwrites directories

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

Impact

ansible-galaxy collection install builds the install directory from the namespace and name fields inside the collection's own metadata. Those fields are not checked for valid identifiers or path containment. A crafted collection can send the install outside the configured collections path. ansible-galaxy then deletes an existing directory the invoking user can write and puts attacker-controlled files there. On provisioning and CI hosts that manage GPU fleets, this can replace content that later runs with fleet-wide reach. This is a separate code path from the role-install flaw CVE-2026-105929.

Who can reach it

Anyone who can get a crafted collection installed: as a local file, a URL, a source directory, a git repository or a dependency. The operator must run ansible-galaxy collection install. 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. Until then, install collections only from trusted, pinned sources 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.