Local file disclosure via unsanitized YAML include paths
Published Jun 9, 2026 · Updated Jun 9, 2026
Path traversal in awxkit for Red Hat Ansible Automation Platform 2.7 allows context-dependent attackers to read local YAML files. The extractFile() function joins unsanitized !include values to a base path without verifying containment, exposing imported contents through AWX resource fields. Exploitation requires a user to import an attacker-supplied YAML file with the nondefault YAML format; plaintext and binary files are not exposed.
Summary
What happened
Path traversal in awxkit for Red Hat Ansible Automation Platform 2.7 allows context-dependent attackers to read local YAML files. The extractFile() function joins unsanitized !include values to a base path without verifying containment, exposing imported contents through AWX resource fields. Exploitation requires a user to import an attacker-supplied YAML file with the nondefault YAML format; plaintext and binary files are not exposed.
The record
- CVE
- CVE-2026-52902
- Published
- Jun 9, 2026
- Updated
- Jun 9, 2026
- Vendor
- 389 Directory Server
- Product
- Red Hat Ansible Automation Platform
- Classifications
- CWE-22, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 9, 2026CVE publishedPublication date reported by the CVE source.
- Jun 9, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo