Quick answers
- Is CVE-2026-32625 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-32625 being exploited in the wild.
- How severe is CVE-2026-32625?
- Critical severity, with a CVSS score of 9.6, published 2 June 2026.
- Which products and versions are affected?
- LibreChat <= 0.8.3.
- Is there a fix for CVE-2026-32625?
- A patch was published on 2026-06-02: Patched in v0.8.4-rc1 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-32625 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-32625?
- Check whether you run LibreChat at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A vulnerability in LibreChat versions up to 0.8.3 exists within the Model Context Protocol (MCP) server integration. The application uses a Zod schema transformation that calls `extractEnvVariable` on user-supplied MCP server URLs, which resolves `${VAR}` placeholders against the server's `process.env`. An authenticated attacker can submit a malicious URL via the `POST /api/mcp/servers` endpoint containing environment variable references (e.g., `${JWT_SECRET}`). During schema validation and subsequent connection testing via `MCPServerInspector.inspect()`, the server resolves these variables and transmits them as part of an HTTP request to an attacker-controlled domain. This results in the exposure of critical secrets such as `CREDS_KEY`, `JWT_SECRET`, and `MONGO_URI`. The issue is patched in version 0.8.4-rc1.
Affected products
- danny-avila LibreChat <= 0.8.3
Timeline
- 2026-06-02: disclosed
- 2026-06-02: advisory
- 2026-06-02: patched: Patched in v0.8.4-rc1