Skip to main content
Mallory
CriticalPublic exploit

LibreChat MCP server URL environment variable secret disclosure

IdentifiersCVE-2026-32625CWE-200· Exposure of Sensitive Information…

CVE-2026-32625 affects LibreChat versions up to and including 0.8.3. The flaw is in the Model Context Protocol (MCP) server integration, where user-supplied MCP server URLs are processed such that ${VAR} placeholders are resolved against the LibreChat server's process.env during Zod schema validation. An authenticated user can create a malicious MCP server configuration whose URL references environment variables and points to an attacker-controlled domain. When LibreChat validates or processes that URL, the server resolves the placeholders and makes a request containing sensitive environment variable values in the URL, disclosing secrets such as CREDS_KEY, CREDS_IV, JWT_SECRET, and MONGO_URI. Because the exposed values include cryptographic material and database credentials, the issue can lead to full compromise of the LibreChat installation without requiring administrative privileges.

Share:
For your environment

Are you exposed to this one?

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.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation discloses high-value server-side secrets to an attacker-controlled endpoint. Exposed data can include encryption keys, initialization vectors, JWT signing secrets, and MongoDB connection credentials. With these materials, an attacker may be able to forge or tamper with authentication tokens, decrypt protected data depending on deployment usage, access or manipulate the backing database, and fully compromise the confidentiality and integrity of the LibreChat deployment. No user interaction or administrative privileges are required beyond authenticated access to create the malicious MCP server configuration.

Mitigation

If you can’t patch tonight, do this now.

If immediate upgrade is not possible, disable or restrict MCP server integration and prevent non-administrative users from creating or modifying MCP server configurations. Block outbound connections from the LibreChat server to untrusted external hosts where feasible, especially for MCP-related traffic. Apply strict egress filtering and monitoring to detect requests containing suspicious URL-embedded secret material. As a precaution, rotate sensitive environment variables and credentials, particularly JWT secrets, encryption keys, and database credentials, if exposure is suspected.

Remediation

Patch, then assume compromise.

Upgrade LibreChat to version 0.8.4-rc1 or later, which patches the vulnerable MCP server URL handling. Ensure that user-controlled MCP server URLs are no longer resolved against process environment variables during validation or request construction. Review and rotate any secrets that may have been exposed prior to patching, including CREDS_KEY, CREDS_IV, JWT_SECRET, MONGO_URI, and any other environment variables accessible to the LibreChat process. Audit logs and outbound requests for evidence of exploitation and unauthorized database or token activity.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
LibrechatLibrechatapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity11

Community discussion across Reddit, Mastodon, and other social sources.