Code execution via unneutralized playbook filename
Published Jul 22, 2026 · Updated Jul 22, 2026
Command injection in Red Hat's Visual Studio Code Ansible Lightspeed extension allows attackers to execute code via a crafted playbook filename. AnsiblePlaybookRunProvider incorporates filename special characters into command construction without neutralizing argument delimiters. Execution requires a victim to run the crafted playbook, after which commands run with the VS Code user's privileges and can read, modify, or delete accessible data.
Summary
What happened
Command injection in Red Hat's Visual Studio Code Ansible Lightspeed extension allows attackers to execute code via a crafted playbook filename. AnsiblePlaybookRunProvider incorporates filename special characters into command construction without neutralizing argument delimiters. Execution requires a victim to run the crafted playbook, after which commands run with the VS Code user's privileges and can read, modify, or delete accessible data.
The record
- CVE
- CVE-2026-44189
- Published
- Jul 22, 2026
- Updated
- Jul 22, 2026
- Vendor
- 389 Directory Server
- Product
- Red Hat Ansible Automation Platform
- Classifications
- CWE-88, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 22, 2026CVE publishedPublication date reported by the CVE source.
- Jul 22, 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