Description

A path traversal vulnerability was found in AWX's project archive extraction. The project_archive action plugin extracts zip and tar archive members by joining the project directory path with the member filename without performing path normalization, boundary validation, or rejecting directory traversal sequences. A malicious archive containing members with path traversal components can write files to arbitrary locations on the execution node's filesystem outside the intended project directory. An attacker who controls the archive content, either through a compromised upstream source, a malicious archive URL, or a man-in-the-middle attack on a plain HTTP connection, can achieve arbitrary file writes as the user performing the extraction, potentially leading to remote code execution through mechanisms such as cron files, SSH authorized keys, or playbook content injection.

Executive Summary

Technical Details

Mitigations

References

Additional Metadata

{
  "score": "7.2",
  "pubDate": "2026-08-24T16:17:22.663Z",
  "pubdate": "2026-08-24T16:17:22.663Z",
  "executiveSummary": "A path traversal vulnerability exists in AWX's project archive extraction functionality, specifically within the project_archive action plugin.\nThe flaw allows a malicious archive containing members with traversal sequences to write files to arbitrary locations on the execution node's filesystem outside the intended project directory.\nThe impact includes potential remote code execution achieved through writing malicious artifacts such as cron files, SSH authorized keys, or injected playbook content.\nThe affected product is AWX, specifically within its archive extraction mechanisms.\nRisk implications are severe, granting attackers the ability to compromise the integrity and confidentiality of the execution node.\nAttacker capabilities require control over the archive content, which can be achieved via a compromised upstream source, a malicious archive URL, or a man-in-the-middle attack conducted over a plain HTTP connection.",
  "technicalDetails": "The root cause of the vulnerability is the improper handling of archive member filenames during extraction within the project_archive action plugin.\nSpecifically, the plugin extracts zip and tar archive members by directly joining the base project directory path with the member filename.\nThe application fails to perform path normalization, boundary validation, or rejection of directory traversal sequences (such as dot-dot-slash patterns).\nThe vulnerable component is the project_archive action plugin responsible for project archive extraction.\nExploitation occurs when an attacker crafts a malicious archive containing members engineered with directory traversal components in their filenames.\nDuring the extraction process, the lack of path sanitization allows these traversal components to escape the intended target directory boundary.\nConsequently, the extraction routine traverses upward in the directory hierarchy and writes arbitrary files to unintended locations on the execution node's filesystem.\nAttack flow involves an attacker supplying the malicious archive through a compromised upstream source, a malicious archive URL, or by intercepting and modifying traffic over an unencrypted plain HTTP connection.\nAuthentication and privilege requirements depend on the context of the workflow execution and access controls governing project archive sources, but exploitation is executed within the privileges of the user performing the extraction.\nPost-exploitation impact ranges from arbitrary file overwrite to full system compromise, enabling remote code execution via persistence mechanisms such as cron jobs, unauthorized SSH keys, or malicious playbook modifications."
}