Loading vulnerability…
CVE-2026-22252 is a critical vulnerability in LibreChat affecting versions prior to v0.8.2-rc2. LibreChat's MCP stdio transport accepts arbitrary commands without validation, allowing an authenticated user to supply attacker-controlled command values through the API. As a result, a single crafted API request can trigger execution of shell commands as root inside the LibreChat container. The issue is remotely exploitable and stems from insufficient restriction of privileged functionality exposed through the MCP stdio transport.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
11 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A previously reported vulnerability in LibreChat arising from the same MCP STDIO architectural weakness that can enable command execution.
An STDIO MCP-related vulnerability in LibreChat mentioned as another finding reported by other researchers.
Improper authorization / command validation issue in LibreChat MCP stdio transport that enables an authenticated user to achieve remote command execution as root inside the container via a single API request.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.