CVE
Red Hat path traversal in ansible-galaxy collection install
Affects Red Hat Ansible Automation Platform and the ansible-core package in RHEL AppStream when ansible-galaxy installs collections from untrusted sources. No fixed version is named yet.
- Exploited
- No known exploitation
- Fix
- See vendor advisory
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. A user or automated process runs ansible-galaxy collection install on a collection from an untrusted or compromised source Installed through Red Hat Ansible Automation Platform or the ansible-core package shipped in RHEL AppStream
Summary
A path traversal flaw in ansible-core's ansible-galaxy collection install lets a remote attacker, without logging in, trick a user into installing a malicious collection that redirects the install outside the collections path. The attacker can then make ansible-galaxy delete an existing directory the user can write to and write attacker-controlled files in its place.
Original 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.
Who should check
Teams running ansible-core through Red Hat Ansible Automation Platform or RHEL 8, 9 or 10 AppStream that run ansible-galaxy collection install on collections from untrusted sources
“Red Hat Ansible Automation Platform ships ansible-core and is affected.”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure12/25Specific setups only, reachable over the network without a login
- Reach10/20Shipped in major Linux distributions
- Severity8.1/10CVSS 8.1
- No patch5/5No fixed version listed; see vendor advisory
What would change the score
- Would score about 85 if added to CISA KEV
- Would score about 80 if CISA's SSVC rates exploitation active
What to do
Check whether your setup matches what the bug needs.
A user or automated process runs ansible-galaxy collection install on a collection from an untrusted or compromised source Installed through Red Hat Ansible Automation Platform or the ansible-core package shipped in RHEL AppStreamWorkaround: Install collections only from trusted sources, and review collection metadata for namespace or name values containing a path separator, '..' sequence, or absolute path before installing.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-130644 (Ansible-core: ansible-core: ansible-galaxy collection install path traversal via unvalidated artifact-derived collection name allows file…), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-130644 (entry last updated 2026-11-18):
Affected:
- Red Hat Migration Toolkit for Applications 8: version range not reported
- Red Hat Migration Toolkit for Virtualization: version range not reported
- Red Hat OpenShift Service Mesh 3: version range not reported
- Red Hat Red Hat Advanced Cluster Management for Kubernetes 2: version range not reported
- Red Hat Red Hat Advanced Cluster Management for Kubernetes 2: version range not reported
- Red Hat Red Hat Ansible Automation Platform 2: version range not reported
- Red Hat Red Hat Ansible Automation Platform 2: version range not reported
- Red Hat Red Hat Ansible Automation Platform 2: version range not reported
- Red Hat Red Hat Ansible Automation Platform 2: version range not reported
- Red Hat Red Hat Ansible Automation Platform 2: version range not reported
- and 78 more affected products, listed on https://cve.now/CVE-2026-130644
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- A user or automated process runs ansible-galaxy collection install on a collection from an untrusted or compromised source (source: https://access.redhat.com/security/cve/cve-2026-130644)
- Installed through Red Hat Ansible Automation Platform or the ansible-core package shipped in RHEL AppStream (source: https://access.redhat.com/security/cve/cve-2026-130644)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, a user action.
Workaround: Install collections only from trusted sources, and review collection metadata for namespace or name values containing a path separator, '..' sequence, or absolute path before installing. (source: https://access.redhat.com/security/cve/cve-2026-130644)
CISA KEV: CVE-2026-130644 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130644 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://bugzilla.redhat.com/show_bug.cgi?id=2574391
- https://access.redhat.com/security/cve/CVE-2026-130644
- https://access.redhat.com/security/cve/cve-2026-130644
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-130644
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-130644"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- mta/mta-rhel9-operator
Version range not reported
- migration-toolkit-virtualization/mtv-rhel9-operator
Version range not reported
- openshift-service-mesh/kiali-rhel9-operator
Version range not reported
- rhacm2/volsync-operator-bundle
Version range not reported
- rhacm2/volsync-rhel9
Version range not reported
- ansible-automation-platform-24/controller-rhel9-operator
Version range not reported
- ansible-automation-platform-24/de-minimal-rhel8
Version range not reported
- ansible-automation-platform-24/de-minimal-rhel9
Version range not reported
- ansible-automation-platform-24/eda-controller-rhel9-operator
Version range not reported
- ansible-automation-platform-24/ee-minimal-rhel8
Version range not reported
- ansible-automation-platform-24/ee-minimal-rhel9
Version range not reported
- ansible-automation-platform-24/hub-rhel8
Version range not reported
- ansible-automation-platform-24/hub-rhel9-operator
Version range not reported
- ansible-automation-platform-24/lightspeed-rhel8
Version range not reported
- ansible-automation-platform-24/lightspeed-rhel9-operator
Version range not reported
- ansible-automation-platform-24/platform-resource-rhel9-operator
Version range not reported
- ansible-automation-platform-25/ansible-dev-tools-rhel8
Version range not reported
- ansible-automation-platform-25/controller-rhel9-operator
Version range not reported
- ansible-automation-platform-25/de-minimal-rhel8
Version range not reported
- ansible-automation-platform-25/de-minimal-rhel9
Version range not reported
- ansible-automation-platform-25/eda-controller-rhel8
Version range not reported
- ansible-automation-platform-25/eda-controller-rhel9-operator
Version range not reported
- ansible-automation-platform-25/ee-minimal-rhel8
Version range not reported
- ansible-automation-platform-25/ee-minimal-rhel9
Version range not reported
- ansible-automation-platform-25/gateway-rhel9-operator
Version range not reported
- ansible-automation-platform-25/hub-rhel8
Version range not reported
- ansible-automation-platform-25/hub-rhel9-operator
Version range not reported
- ansible-automation-platform-25/lightspeed-rhel8
Version range not reported
- ansible-automation-platform-25/lightspeed-rhel9-operator
Version range not reported
- ansible-automation-platform-25/platform-resource-rhel9-operator
Version range not reported
- ansible-automation-platform-26/ansible-dev-tools-rhel9
Version range not reported
- ansible-automation-platform-26/controller-rhel9-operator
Version range not reported
- ansible-automation-platform-26/de-minimal-rhel9
Version range not reported
- ansible-automation-platform-26/de-supported-rhel9
Version range not reported
- ansible-automation-platform-26/eda-controller-rhel9
Version range not reported
- ansible-automation-platform-26/eda-controller-rhel9-operator
Version range not reported
- ansible-automation-platform-26/ee-minimal-rhel9
Version range not reported
- ansible-automation-platform-26/ee-supported-rhel9
Version range not reported
- ansible-automation-platform-26/gateway-rhel9-operator
Version range not reported
- ansible-automation-platform-26/hub-rhel9
Version range not reported
- ansible-automation-platform-26/hub-rhel9-operator
Version range not reported
- ansible-automation-platform-26/lightspeed-rhel9
Version range not reported
- ansible-automation-platform-26/lightspeed-rhel9-operator
Version range not reported
- ansible-automation-platform-26/platform-resource-rhel9-operator
Version range not reported
- ansible-automation-platform-26/platform-resource-runner-rhel9
Version range not reported
- ansible-automation-platform-27/aap-cloud-billing-operator-rhel9
Version range not reported
- ansible-automation-platform-27/ansible-devspaces-rhel9
Version range not reported
- ansible-automation-platform-27/ansible-dev-tools-rhel9
Version range not reported
- ansible-automation-platform-27/controller-rhel9-operator
Version range not reported
- ansible-automation-platform-27/de-minimal-rhel9
Version range not reported
- ansible-automation-platform-27/de-supported-rhel9
Version range not reported
- ansible-automation-platform-27/eda-controller-rhel9
Version range not reported
- ansible-automation-platform-27/eda-controller-rhel9-operator
Version range not reported
- ansible-automation-platform-27/ee-control-plane-rhel9
Version range not reported
- ansible-automation-platform-27/ee-minimal-rhel9
Version range not reported
- ansible-automation-platform-27/ee-supported-rhel9
Version range not reported
- ansible-automation-platform-27/gateway-rhel9-operator
Version range not reported
- ansible-automation-platform-27/hub-rhel9
Version range not reported
- ansible-automation-platform-27/hub-rhel9-operator
Version range not reported
- ansible-automation-platform-27/lightspeed-rhel9
Version range not reported
- ansible-automation-platform-27/lightspeed-rhel9-operator
Version range not reported
- ansible-automation-platform-27/metrics-service-rhel9-operator
Version range not reported
- ansible-automation-platform-27/platform-resource-rhel9-operator
Version range not reported
- ansible-automation-platform-27/platform-resource-runner-rhel9
Version range not reported
- ansible-automation-platform-tech-preview/ansible-devspaces-rhel9
Version range not reported
- ansible-automation-platform-tech-preview/metrics-service-rhel9-operator
Version range not reported
- ansible-core
Version range not reported
- ansible-automation-platform/ee-minimal-rhel8
Version range not reported
- ansible-automation-platform/ee-minimal-rhel9
Version range not reported
- ansible-automation-platform-tech-preview/ee-minimal-rhel8
Version range not reported
- ansible-automation-platform-tech-preview/ee-minimal-rhel9
Version range not reported
- discovery/discovery-server-rhel9
Version range not reported
- ansible-core
Version range not reported
- ansible-core
Version range not reported
- ansible-core
Version range not reported
- rhel-cla/installer-rhel10
Version range not reported
- openshift4/ose-ansible-rhel9-operator
Version range not reported
- openshift5/ose-ansible-rhel9-operator
Version range not reported
- openstack-ansible-core
Version range not reported
- rhosp-rhel9/openstack-neutron-server
Version range not reported
- rhosp-rhel9/openstack-tripleoclient
Version range not reported
- rhoso-operators/ee-openstack-ansible-ee-rhel9
Version range not reported
- ansible-core
Version range not reported
- rhui5/installer-tp-rhel9
Version range not reported
- rhui5/rhua-tp-rhel9
Version range not reported
- ansible-automation-platform/bootc-automation-portal-rhel9
Version range not reported
- stf/service-telemetry-rhel9-operator
Version range not reported
- stf/smart-gateway-rhel9-operator
Version range not reported
Evidence 4
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-130644 |
| Record | NVD · CVE-2026-130644 |
| Write-ups 1Establishes: Technical detail and context. | |
| Report | bugzilla.redhat.com · show_bug.cgi?id=2574391 |
| Other links 1 | |
| Link | access.redhat.com · security/cve/CVE-2026-130644 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-130644
Is CVE-2026-130644 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
A crafted collection can make ansible-galaxy collection install delete an existing directory that the invoking user can write to. It then writes attacker-controlled files to that location, outside the collections path.Source: access.redhat.com
Am I affected, and how do I check?
The advisory lists Red Hat Ansible Automation Platform 2 and the ansible-core package shipped in RHEL AppStream, along with several other Red Hat products. The bug requires running ansible-galaxy collection install on a collection from an untrusted or compromised source. Check the installed ansible-core version with ansible --version.Source: access.redhat.com
How do I fix CVE-2026-130644?
No fixed version is named in the advisory yet. It says fixes will be provided for maintained streams, so check the advisory for updated versions or patch identifiers.Source: access.redhat.com
What if there's no patch?
Install collections only from trusted sources. Before installing, review collection metadata for namespace or name values that contain a path separator, a '..' sequence, or an absolute path.Source: access.redhat.com