CVE-2026-130644: 
Linux Red Hat Analyse et atténuation de la vulnérabilité

Aperçu

CVE-2026-130644 is a path traversal vulnerability in ansible-core affecting the ansible-galaxy collection install command. When installing a collection, the install destination directory is derived from the namespace and name fields in the collection artifact's metadata (MANIFEST.json or galaxy.yml) without validating these values for path containment or well-formed collection identifiers. A malicious collection artifact can exploit this to redirect the install destination outside the configured collections path, enabling arbitrary file writes and directory deletion. Affected products include ansible-core across multiple Red Hat Ansible Automation Platform versions (2.4 through 2.7), Red Hat Enterprise Linux AppStream, and related Red Hat products. Disclosed on November 18, 2026, it carries a CVSS v3.1 base score of 8.1 (High) (Red Hat CVE, Github Advisory).

Détails techniques

The root cause is CWE-22 (Improper Limitation of a Pathname to a Restricted Directory), where ansible-galaxy fails to validate that the namespace and name fields in collection metadata do not contain path separators, .. sequences, or absolute paths before constructing the install destination directory. An attacker crafts a collection artifact with a malicious name value (e.g., containing ../../ or an absolute path) in MANIFEST.json's collection_info or galaxy.yml. When a user or automated process runs ansible-galaxy collection install against this artifact — delivered as a local file, remote URL, source directory, git repository, or transitive dependency — ansible-galaxy first deletes any pre-existing directory at the computed (traversed) destination, then writes the attacker-controlled artifact contents there. Notably, collection signature verification is optional and does not prevent this issue (Red Hat Bugzilla, Red Hat CVE).

Impact

Successful exploitation allows an attacker to delete any existing directory writable by the invoking user and write attacker-controlled files to that location outside the intended collections path. This can lead to arbitrary code execution if critical files (e.g., scripts, libraries, configuration files) are overwritten, as well as denial of service through deletion of important directories. Confidentiality impact is rated None by CVSS, but integrity and availability are both rated High, reflecting the potential to corrupt or replace system files and disrupt operations. The attack requires user interaction (a user or automated process must install the malicious collection), limiting but not eliminating risk in CI/CD pipelines and automated provisioning environments (Red Hat CVE, Github Advisory).

Exploitabilité

As of the disclosure date (November 18, 2026), there is no public proof-of-concept exploit and no evidence of in-the-wild exploitation (Red Hat CVE). The EPSS score is 0.0, indicating very low current exploitation probability. The vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog. Exploitation requires convincing a user or automated process to install a malicious collection, which could occur via supply chain compromise, dependency confusion, or social engineering. The vulnerability was originally reported by researcher rootvector2 via GitHub (ansible/ansible PR #87088) (Red Hat CVE).

Étapes d’exploitation

  1. Craft a malicious collection artifact: Create a collection archive with a MANIFEST.json (or galaxy.yml) where the name field contains a path traversal sequence, e.g., name: "../../target_directory" or an absolute path like name: "/etc/cron.d/malicious".
  2. Package the artifact: Bundle the malicious metadata and attacker-controlled payload files into a valid-looking .tar.gz collection archive.
  3. Deliver the artifact: Host the malicious collection at a remote URL, publish it to a public or private Ansible Galaxy mirror, include it as a dependency in a requirements.yml file, or distribute it as a local file or git repository.
  4. Trigger installation: Wait for or socially engineer a target user or automated CI/CD pipeline to run ansible-galaxy collection install <malicious_artifact> or install a legitimate collection that depends on the malicious one.
  5. Achieve file write: ansible-galaxy resolves the install path using the unvalidated name field, deletes the existing directory at the traversed path (if writable by the invoking user), and extracts the attacker-controlled files to that location outside the collections directory.
  6. Achieve code execution (optional): If the written files overwrite executable scripts, cron jobs, Python libraries, or Ansible playbooks, the attacker achieves code execution in the context of the user or service that next runs those files (Red Hat Bugzilla, Red Hat CVE).

Indicateurs de compromis

  • File System: Unexpected files or directories appearing outside the configured Ansible collections path (e.g., ~/.ansible/collections/ or /usr/share/ansible/collections/); missing or replaced directories that were previously present and writable by the ansible-galaxy invoking user; unexpected modifications to scripts, cron jobs, or Python libraries.
  • Logs: ansible-galaxy output showing collection install paths resolving to unexpected locations (e.g., paths containing .. or absolute paths outside the collections directory); errors or warnings related to directory deletion during collection install.
  • Network: Outbound connections from the ansible-galaxy process to unexpected or untrusted remote URLs during collection installation; collection downloads from non-standard or unrecognized Ansible Galaxy mirrors or repositories.
  • Process: Unexpected processes spawned after collection installation, particularly if overwritten scripts or cron jobs are executed; ansible-galaxy processes accessing file paths outside the expected collections directory tree.

Atténuation et solutions de contournement

Red Hat has confirmed a patch is available; users should update ansible-core to a patched version once released for their specific platform stream (Github Advisory). As an immediate workaround, Red Hat recommends installing collections only from trusted, verified sources and manually reviewing MANIFEST.json (collection_info) or galaxy.yml metadata for any namespace or name values containing path separators (/, \), .. sequences, or absolute paths before installation. Avoid installing collections from requirements.yml files or dependency chains that reference untrusted repositories or mirrors. Restricting write permissions on directories where ansible-galaxy operates can also limit the blast radius of exploitation (Red Hat CVE).

Réactions de la communauté

Red Hat Product Security acknowledged the vulnerability and confirmed that both Red Hat Ansible Automation Platform and Red Hat Enterprise Linux (AppStream) are affected. The original reporter is credited as rootvector2 via a GitHub pull request (ansible/ansible PR #87088). The CVE was noted on Mastodon by @thehackerwire shortly after disclosure. No significant broader media coverage or notable researcher commentary beyond the initial disclosure has been observed as of the publication date (Red Hat CVE, Red Hat Bugzilla).

Ressources supplémentaires

État de correction de la distribution Linux

Corrigez la disponibilité entre les grandes distributions Linux et leurs versions.

Ubuntu

Inconnu

bionic (esm-apps)

ansible

Inconnu

devel

ansible

Inconnu

focal (esm-apps)

ansible

Inconnu

jammy

ansible

Inconnu

jammy (esm-apps)

ansible

Inconnu

noble

ansible

Inconnu

noble (esm-apps)

ansible

Inconnu

resolute

ansible

Inconnu

Source: Ce rapport a été généré à l’aide de l’IA

Connexe Linux Red Hat Vulnérabilités :

CVE ID

Gravité

Partition

Technologies

Nom du composant

Exploit CISA KEV

A corrigé

Date de publication

CVE-2026-130644HIGH8.1
  • Linux Red Hat logoLinux Red Hat
  • ansible-core
NonNonNov 18, 2026
CVE-2026-105929HIGH8.1
  • Linux Red Hat logoLinux Red Hat
  • ansible-core
NonNonNov 18, 2026
CVE-2026-114938HIGH8.1
  • Amazon Corretto JDK logoAmazon Corretto JDK
  • java-21-openjdk-static-libs-fastdebug
NonOuiNov 17, 2026
CVE-2026-119192HIGH7.5
  • Chainguard logoChainguard
  • argo-workflows-3.6
NonOuiNov 17, 2026
CVE-2026-6949HIGH7.5
  • Samba logoSamba
  • ctdb-tests
NonOuiNov 16, 2026

Évaluation gratuite des vulnérabilités

Évaluez votre posture de sécurité cloud

Évaluez vos pratiques de sécurité cloud dans 9 domaines de sécurité afin d’évaluer votre niveau de risque et d’identifier les lacunes dans vos défenses.

Évaluation de la demande

Ressources Wiz supplémentaires

Obtenez une démo personnalisée

Prêt(e) à voir Wiz en action ?

"La meilleure expérience utilisateur que j’ai jamais vue, offre une visibilité totale sur les workloads cloud."
David EstlickRSSI
"Wiz fournit une interface unique pour voir ce qui se passe dans nos environnements cloud."
Adam FletcherChef du service de sécurité
"Nous savons que si Wiz identifie quelque chose comme critique, c’est qu’il l’est réellement."
Greg PoniatowskiResponsable de la gestion des menaces et des vulnérabilités