# 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.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H`)
- **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 available:** No
- **Published:** 18 Nov 2026
- **Updated:** 18 Nov 2026
- **Also known as:** GHSA-qvg5-6mh8-jpg9, UBUNTU-CVE-2026-130644

## 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 (Improper Limitation of a Pathname to a Restricted Directory)

## 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: Red Hat Ansible Automation Platform, Redhat Ansible Core, Redhat Ansible Portal, Red Hat Discovery, Red Hat Enterprise Linux, Red Hat Openshift, OpenStack, Redhat Rhel Cla, Redhat Rhui, Red Hat Satellite.

CPE match criteria (CPE 2.3):

- `cpe:2.3:a:redhat:ansible_automation_platform:2:*:*:*:*:*:*:*`
- `cpe:2.3:a:redhat:ansible_core:2:*:*:*:*:*:*:*`
- `cpe:2.3:a:redhat:ansible_portal:2:*:*:*:*:*:*:*`
- `cpe:2.3:a:redhat:discovery:2:*:el8:*:*:*:*:*`
- `cpe:2.3:a:redhat:enterprise_linux:10:*:*:*:*:*:*:*`
- `cpe:2.3:a:redhat:enterprise_linux:8:*:*:*:*:*:*:*`
- `cpe:2.3:a:redhat:enterprise_linux:9:*:*:*:*:*:*:*`
- `cpe:2.3:a:redhat:openshift:4:*:*:*:*:*:*:*`
- `cpe:2.3:a:redhat:openshift:5:*:*:*:*:*:*:*`
- `cpe:2.3:a:redhat:openstack:17.1:*:*:*:*:*:*:*`
- `cpe:2.3:a:redhat:rhel_cla:2:*:*:*:*:*:*:*`
- `cpe:2.3:a:redhat:rhui:5:*:el9:*:*:*:*:*`
- `cpe:2.3:a:redhat:satellite: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.

## Is CVE-2026-130644 being exploited?

There is no known exploitation of CVE-2026-130644 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-130644 and fix it if it is affected.

What it is: 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.
Exploitation: There is no known exploitation of CVE-2026-130644 in the wild and no public exploit code.
Exposure: An affected version is exposed as installed. No special setting or call is needed.

Affected product: Red Hat Migration Toolkit for Applications 8. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-130644/ (Markdown: https://insights.sbomify.com/CVE-2026-130644/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-130644
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-130644
- OSV: https://osv.dev/vulnerability/CVE-2026-130644

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-130644/
Summaries are generated and may contain mistakes; the official description above is the record.
