Public vulnerability disclosure

CVE-2026-71364

Awx: project archive extraction allows path traversal file writes

publishedCWE-22

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.

Technical severity7.2 highCVSS 3.1 · CNA: redhat
Published2026-08-24Source updated 2026-11-04
Collected2026-11-052 attributed sources

Fixes and workarounds

Workaround

There is no complete mitigation for this vulnerability other than applying the update when available. However, the following measures reduce exposure: 1. Avoid using archive-type projects (scm_type='archive') until the fix is applied. Use Git-based projects (scm_type='git') instead where possible, as these do not use the vulnerable extraction code path. 2. Ensure all archive source URLs use HTTPS with valid certificates to prevent man-in-the-middle attacks on archive downloads. 3. Only configure archive-type projects with sources from trusted, verified providers. 4. Restrict the ability to create and modify projects to trusted administrators. 5. In containerized deployments, review execution environment container configurations to minimize host volume mounts and ensure the extraction runs with minimal filesystem permissions.

Source: CNA: redhat

Affected products and versions

Affected products, source version ranges and reporting authorities
ProductVersionsAuthority
Red Hat Ansible Automation Platform 2.5 for RHEL 8
Red Hat
automation-controller
https://access.redhat.com/downloads/content/package-browser/
≥ 0:4.6.32-1.el8ap; < * (unaffected, rpm)
Other versions: affected
CNA: redhat
Red Hat Ansible Automation Platform 2.5 for RHEL 9
Red Hat
automation-controller
https://access.redhat.com/downloads/content/package-browser/
≥ 0:4.6.32-1.el9ap; < * (unaffected, rpm)
Other versions: affected
CNA: redhat
Red Hat Ansible Automation Platform 2.6 for RHEL 9
Red Hat
automation-controller
https://access.redhat.com/downloads/content/package-browser/
≥ 0:4.7.16-1.el9ap; < * (unaffected, rpm)
Other versions: affected
CNA: redhat
Red Hat Ansible Automation Platform 2.6
Red Hat
ansible-automation-platform-26/controller-rhel9
https://catalog.redhat.com/software/containers/
≥ 1787244009; < * (unaffected, rpm)
Other versions: affected
CNA: redhat
Red Hat Ansible Automation Platform 2.7
Red Hat
ansible-automation-platform-27/controller-rhel9
https://catalog.redhat.com/software/containers/
≥ 1787220257; < * (unaffected, rpm)
Other versions: affected
CNA: redhat

Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.

CVSS assessments

CVSS scores, vectors and reporting authorities
Version / scoreVectorAuthority
3.1 / 7.2
high
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:HCNA: redhat

Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

References

For agents and automation

Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.

Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.

Endpoints and access details

https://api.y2.dev/api/v2/cyber/cves
https://api.y2.dev/api/v2/cyber/cves/{cveId}

A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.

For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.

Agent access JSON · OpenAPI · CVE API guide