Skip to main content
Menu
CVEs

CVE

Red Hat file write and deletion via ansible-galaxy role installer

CVE-2026-105929EUVD-2026-128411GHSA-65G3-4M89-FC5MPublished Updated Summary written by a model

8.1HighCNA
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. The operator installs a role whose meta/requirements.yml, including transitive dependencies, contains a role name with ../ or an absolute path. Existing role directory removal and replacement outside the roles path requires ansible-galaxy role install --force.

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.

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

cve.now Index

35Pcve.now Index 35 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • 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.

    The operator installs a role whose meta/requirements.yml, including transitive dependencies, contains a role name with ../ or an absolute path. Existing role directory removal and replacement outside the roles path requires ansible-galaxy role install --force.
  • 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.

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-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"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  4. Record last updated

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/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

Evidence 4

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
Linkaccess.redhat.com · security/cve/CVE-2026-105929
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-105929
RecordNVD · CVE-2026-105929
Write-ups 1Establishes: Technical detail and context.
Reportbugzilla.redhat.com · show_bug.cgi?id=2546288

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-105929

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: cve.now feed data

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: access.redhat.com, cve.org

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: access.redhat.com, cve.org

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: access.redhat.com, cve.org

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: access.redhat.com, cve.org

More CVEs