dbcve.org
LibrechatApplication

CVE-2026-22252

CRITICAL · 9.9 CVSS v3.1 Published 2026-01-12
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
LibreChat is a ChatGPT clone with additional features. Prior to v0.8.2-rc2, LibreChat's MCP stdio transport accepts arbitrary commands without validation, allowing any authenticated user to execute shell commands as root inside the container through a single API request. This vulnerability is fixed in v0.8.2-rc2.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

LibreChat's MCP stdio transport lacks command validation, allowing any authenticated user to inject and execute arbitrary shell commands as root inside the container through a single API request. This is a critical command injection vulnerability in the MCP (Model Context Protocol) stdio transport component.

MitigationUpgrade to LibreChat v0.8.2-rc2 or later to obtain the fixed version. Review container isolation policies and audit access logs for signs of exploitation, as the vulnerability allows root-level command execution.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
LibrechatApplication
Affected:= 0.8.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed LibreChat version
    Check the package.json file in the LibreChat installation directory, or run 'npm list librechat' or 'cat package.json | grep version' in the application root
    Affected if Version is exactly 0.8.2 (note: only this specific version is affected)
  2. Locate MCP stdio transport configuration
    Search for MCP stdio configuration files in the LibreChat config directory, typically under config/mcp or similar paths. Look for files containing 'stdio' or 'mcp' in the configuration
    Affected if MCP stdio transport is enabled and configured in the environment
  3. Verify API authentication settings
    Inspect the LibreChat authentication configuration (usually in .env or config files). Check if API endpoints accept authenticated user sessions without additional authorization controls
    Affected if API is accessible to authenticated users without command-level authorization constraints
  4. Confirm container execution context
    Check if LibreChat is running inside a container and inspect the container's user/privilege settings (docker inspect or container orchestration config)
    Affected if LibreChat runs inside a container where the application process executes as root (UID 0)

Environment is affected if running exactly LibreChat version 0.8.2 with the MCP stdio transport enabled and the API accessible to authenticated users running in a root-privileged container context

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Upgrade to LibreChat v0.8.2-rc2 or later to obtain the fixed version. Review container isolation policies and audit access logs for signs of exploitation, as the vulnerability allows root-level command execution.

Recommended fix High confidence

v0.8.2-rc2 or later stable release

  1. 1. Backup your LibreChat installation and any persistent data volumes before upgrading
  2. 2. Stop the running LibreChat container or service
  3. 3. Pull the fixed version: docker pull libreworker/librechat:v0.8.2-rc2 (or a later stable release if available)
  4. 4. Update your docker-compose.yml or deployment configuration to use the fixed version
  5. 5. Restart the LibreChat service
  6. 6. Verify the upgrade was successful by checking the version in the UI or via API
  7. 7. Test that MCP stdio transport now properly validates commands

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Librechat Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,260
Get the patch applied

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,816.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-22252 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-22252 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data