CVE-2026-130644: Ansible-core: ansible-core: ansible-galaxy collection install path traversal via unvalidated artifact-derived collection name allows file writes and directory deletion outside the collections path
A flaw was found in ansible-core. When installing a collection with ansible-galaxy collection install, the install destination directory is derived from the namespace and name fields declared inside the collection artifact's own metadata (MANIFEST.json's collectioninfo, or galaxy.yml for directory- or git-sourced installs), without validating that these values are well-formed collection identifiers or confirming that the resulting path stays within the configured collections directory. A specially crafted collection artifact can set an absolute-path or traversal-style name value that redirects the install destination outside the collections path. Before extracting the artifact's contents, ansible-galaxy removes any pre-existing directory at the computed destination and then writes the artifact's files there. An attacker able to get a user or an automated process to run ansible-galaxy collection install against a malicious artifact -- supplied as a local file, a remote URL, a source directory, a git repository, or referenced as a dependency -- can cause deletion of an existing directory writable by the invoking user and creation of attacker-controlled files at that same location, outside the collections directory. Collection signature verification is optional and does not prevent this issue.
Other sources
A path traversal flaw was found in ansible-core. When installing a collection with ansible-galaxy collection install, the install destination directory is derived from the namespace and name fields declared inside the collection artifact's own metadata, which are not validated as well-formed collection identifiers or checked for path containment. A malicious collection artifact -- delivered as a local file, a remote URL, a source directory, a git repository, or as a dependency -- can use a crafted name value to redirect the install destination outside the configured collections path, causing ansible-galaxy to delete an existing directory writable by the invoking user and then write attacker-controlled files to that location.
— MITRE
Affected Software
Event History
Frequently Asked Questions
Who is exposed to this issue?
Users and automated processes that run ansible-galaxy collection install against attacker-controlled or untrusted collection content are exposed. The malicious collection may be supplied as a local file, remote URL, source directory, Git repository, or dependency.
What does an attacker need to exploit it?
An attacker needs to cause the target user or automation to install a specially crafted collection artifact. No privileges are required by the attacker beyond influencing the collection source that is installed.
What is the impact in the context of the invoking account?
The install process can delete an existing directory at the attacker-directed destination if that directory is writable by the invoking user. It can then create attacker-controlled files outside the configured collections directory.
What can be done before a fix is available?
Avoid installing collections from untrusted files, URLs, directories, Git repositories, or dependency chains. Restrict collection installation automation to vetted sources and accounts with minimal write access.