Path Traversal in Ansible Lightspeed Model Context Protocol (MCP) server (CVE-2026-44192)
Summary
Path traversal in Ansible Lightspeed Model Context Protocol (MCP) server (CVE-2026-44192). Confidential information can be exposed externally.
Original description
The description as published by the source.
A flaw was found in the Ansible Lightspeed Model Context Protocol (MCP) server. This vulnerability, known as path traversal, allows an attacker to manipulate an AI agent through indirect prompt injection. By doing so, the attacker can cause the server to write files to unauthorized locations on the user's system. This can result in the exposure of sensitive host information and enable the attacker to execute malicious commands, potentially leading to a full system compromise.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-44192 has been found in Ansible Lightspeed Model Context Protocol (MCP) server.
Confidential information can be exposed externally. CVSS score: 6.6/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Ansible Lightspeed Model Context Protocol (MCP) server CVE-2026-44192" on the vendor's site.
CVE-2026-44192 (Ansible Lightspeed Model Context Protocol (MCP) server) — CWE-22 / CVSS v3 6.6
Attack vector: local / unauthenticated
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Path traversal (CWE-22) exists in Ansible Lightspeed Model Context Protocol (MCP) server.
Check the vendor advisory for the affected versions of Ansible Lightspeed Model Context Protocol (MCP) server.
Severity: Medium (CVSS 6.6/10). Confidential information can be exposed externally.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Ansible Lightspeed Model Context Protocol (MCP) server を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web nvd.nist.gov
- web secalert@redhat.com
- web secalert@redhat.com
- web github.com