Skip to content
VulniPulse
Medium4.7Red Hat Linux

Medium [CVE-2026-52902] Awxkit: path traversal via yaml !include directive

This medium-severity Red Hat Linux advisory covers CVE-2026-52902 affecting Red Hat Ansible Automation Platform 2.

CVE-2026-52902 Published Jun 9, 2026Updated by vendor Jun 9, 2026
Affected products & platforms
Red Hat LinuxUnclassified
Open vendor advisory

Android app · Google Play

Monitor future Red Hat Linux CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Summary

A path traversal vulnerability was found in awxkit, the CLI tool for AWX. The YAML!include directive does not sanitize file paths, allowing an attacker to craft a malicious YAML file that reads arbitrary YAML-formatted files from the local filesystem when a user imports it using "awx --conf.format yaml import".

This is a client-side vulnerability requiring user interaction. awxkit as a bundled Python dependency found in ee-supported and platform-resource-runner containers for ansible-automation-platform and as part of the automation-controller RPM. Red Hat severity: Moderate — CVSS 4.7 (CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N).

Weakness: CWE-22. Affected Red Hat products: Red Hat Ansible Automation Platform 2.

Red Hat does not currently list a fixing RHSA for this CVE.

Affected versions

No affected-version range was extracted from the source record. The vendor advisory is authoritative — check it before change work.

Official advisory · high-confidence parse· fetched 33 minutes ago·verify at source

Fixed versions

No fixed release is recorded yet. That does not prove no patch exists — confirm against the vendor advisory.

Official advisory · high-confidence parse· fetched 33 minutes ago·verify at source

Mitigation checklist

Recommended fix / mitigation
  • The following practices would help for avoiding exposure to this flaw: 1) Prioritize the default JSON import format instead of YAML. 2) Avoid importing YAML files from untrusted sources.

Official advisory · high-confidence parse· fetched 33 minutes ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.