Quick answers
- Is CVE-2026-44653 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-44653 being exploited in the wild.
- How severe is CVE-2026-44653?
- Medium severity, with a CVSS score of 6.5, published 2 June 2026.
- Which products and versions are affected?
- LibreChat <= 0.8.3.
- Is there a fix for CVE-2026-44653?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-44653 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-44653?
- 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
An information disclosure vulnerability exists in LibreChat's MCP server integration due to improper redaction of sensitive configuration data. In versions up to 0.8.3, the `GET /api/mcp/servers` and `GET /api/mcp/servers/:serverName` endpoints return decrypted configuration objects that include plaintext values for `apiKey.key` and `oauth.client_secret`. The root cause is located in the `ServerConfigsDB.mapDBServerToParsedConfig()` function, which decrypts these secrets before they are passed to the route handlers. Any authenticated user with 'VIEW' permissions on a shared MCP server can exfiltrate these credentials. The vulnerability is addressed in version 0.8.4 by implementing response sanitization.
Affected products
- danny-avila LibreChat <= 0.8.3
Timeline
- 2026-03-13: other: Vulnerability confirmed in testing environment
- 2026-06-02: disclosed: Security advisory published by vendor
- 2026-06-02: advisory: CVE-2026-44653 published