cve.bz

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

8.1 high

High (8.1) in red hat.

On this page
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.

Severity

CVSS 3.1

8.1 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H
CWE
CWE-22 Improper Limitation of a Pathname to a Restricted Directory (Path traversal)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
Assigned by
redhat (CNA)
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-130644 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-130644?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-130644?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-130644 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

  • red hat:migration toolkit for applications 8
  • red hat:migration toolkit for virtualization
  • red hat:openshift service mesh 3
  • red hat:red hat advanced cluster management for kubernetes 2
  • red hat:red hat ansible automation platform 2
  • red hat:red hat ansible automation platform ansible core 2
  • red hat:red hat discovery 2
  • red hat:red hat enterprise linux 10
  • red hat:red hat enterprise linux 8
  • red hat:red hat enterprise linux 9
  • red hat:red hat enterprise linux command line assistant
  • red hat:red hat openshift container platform 4
  • red hat:red hat openshift container platform 5
  • red hat:red hat openstack platform 17.1
  • red hat:red hat openstack platform 18.0
  • red hat:red hat satellite 6
  • red hat:red hat update infrastructure 5
  • red hat:self-service automation portal 2
  • red hat:service telemetry framework 1.5

Attack patterns (CAPEC)

  • CAPEC-64 Using Slashes and URL Encoding Combined to Bypass Validation Logic Likelihood: High · Severity: High
  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-78 Using Escaped Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-79 Using Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-126 Path Traversal Likelihood: High · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON