CVE-2026-130644 Path traversal in Migration Toolkit for Applications 8
A malicious collection artifact can make ansible-galaxy delete directories and write files outside the collections path; Ansible users should care.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Harmful if only installed
- No
- Needs a specific call
- No
- Fix
- None listed
What is CVE-2026-130644?
CVE-2026-130644 is a high-severity path traversal vulnerability in Red Hat Migration Toolkit for Applications 8, published on 18 Nov 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Official description
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.
Weakness: CWE-22
Which versions are affected by CVE-2026-130644?
It affects 10 products.
An affected version is exposed as installed. No special setting or call is needed.
Products include Red Hat Ansible Automation Platform, Redhat Ansible Core, Redhat Ansible Portal, Red Hat Discovery, Red Hat Enterprise Linux, Red Hat Openshift and 4 more.
CPE match criteria (13)
| CPE 2.3 | Versions |
|---|---|
cpe:2.3:a:redhat:ansible_automation_platform:2:*:*:*:*:*:*:* | 2 |
cpe:2.3:a:redhat:ansible_core:2:*:*:*:*:*:*:* | 2 |
cpe:2.3:a:redhat:ansible_portal:2:*:*:*:*:*:*:* | 2 |
cpe:2.3:a:redhat:discovery:2:*:el8:*:*:*:*:* | 2 |
cpe:2.3:a:redhat:enterprise_linux:10:*:*:*:*:*:*:* | 10 |
cpe:2.3:a:redhat:enterprise_linux:8:*:*:*:*:*:*:* | 8 |
cpe:2.3:a:redhat:enterprise_linux:9:*:*:*:*:*:*:* | 9 |
cpe:2.3:a:redhat:openshift:4:*:*:*:*:*:*:* | 4 |
cpe:2.3:a:redhat:openshift:5:*:*:*:*:*:*:* | 5 |
cpe:2.3:a:redhat:openstack:17.1:*:*:*:*:*:*:* | 17.1 |
cpe:2.3:a:redhat:rhel_cla:2:*:*:*:*:*:*:* | 2 |
cpe:2.3:a:redhat:rhui:5:*:el9:*:*:*:*:* | 5 |
cpe:2.3:a:redhat:satellite:6:*:*:*:*:*:*:* | 6 |
How do I fix CVE-2026-130644?
No fix has been published for CVE-2026-130644 yet. Limit exposure of the affected software until one is available.
Upgrade, and resolve every user-supplied path against an allowed base folder before opening it. More about Path traversal.
Is CVE-2026-130644 being exploited?
There is no known exploitation of CVE-2026-130644 in the wild and no public exploit code.
Sources
Also known as GHSA-qvg5-6mh8-jpg9, UBUNTU-CVE-2026-130644.