{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-44191 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-44191 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-44191 is a high-severity command injection vulnerability in Red Hat Ansible Automation Platform 2, published on 22 Jul 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-44191 and fix it if it is affected.\n\nWhat it is: CVE-2026-44191 is a high-severity command injection vulnerability in Red Hat Ansible Automation Platform 2, published on 22 Jul 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-44191 in the wild and no public exploit code.\n\nAffected product: Red Hat Ansible Automation Platform 2. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-44191/ (Markdown: https://insights.sbomify.com/CVE-2026-44191/index.md)","id":"CVE-2026-44191","markdown":"https://insights.sbomify.com/CVE-2026-44191/index.md","name":"CVE-2026-44191","record":{"aliases":["GHSA-63fx-4hcp-68gg"],"analysis":{"component_type":"developer_tool","fix_type":"patch","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"VS Code Ansible extension","requires_auth":"none","summary":"Attackers can execute arbitrary code on a developer's machine via command injection in Ansible Lightspeed VS Code extension settings.","user_interaction":"required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-78","name":"Improper Neutralization of Special Elements used in an OS Command"}],"description":"A flaw was found in the Visual Studio Code Ansible Lightspeed extension. This command injection vulnerability (CWE-78) arises from improper handling of the ansible.executionEnvironment.containerOptions and ansible.executionEnvironment.volumeMounts settings, allowing an attacker to inject shell separators. This can be triggered automatically during Language Server initialization or manually when executing a playbook. Successful exploitation leads to remote code execution (RCE) on the victim's machine with the privileges of the Visual Studio Code user, potentially resulting in a complete system compromise.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Command injection in Red Hat Ansible Automation Platform 2","id":"CVE-2026-44191","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"command_injection","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Ansible-lightspeed: ansible lightspeed mcp server: remote code execution and data exfiltration via path traversal","id":"CVE-2026-44192"},"packages":[],"prev":{"headline":"Command injection in Red Hat Ansible Automation Platform 2","id":"CVE-2026-44190"},"products":["Red Hat Ansible Automation Platform 2"],"published":"2026-07-22","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-07-22","vendors":["Red Hat"]},"summary":"Attackers can execute arbitrary code on a developer's machine via command injection in Ansible Lightspeed VS Code extension settings.","url":"https://insights.sbomify.com/CVE-2026-44191/"}