Quick answers
- Is CVE-2026-54037 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-54037 being exploited in the wild.
- How severe is CVE-2026-54037?
- Medium severity, with a CVSS score of 6.5, published 25 June 2026.
- Which products and versions are affected?
- LibreChat < 0.8.4-rc1.
- Is there a fix for CVE-2026-54037?
- 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-54037 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-54037?
- 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
The vulnerability exists in the 'POST /api/convos/duplicate' endpoint in 'api/server/routes/convos.js'. While a previous fix (CVE-2025-7105) implemented 'forkIpLimiter' and 'forkUserLimiter' for the '/fork' endpoint, the '/duplicate' endpoint performs identical expensive database operations—including fetching, cloning, and batch-writing messages to MongoDB—without any rate limiting. An authenticated attacker can exploit this to exhaust MongoDB write throughput, fill disk space with redundant records, or trigger Out-of-Memory (OOM) errors during service restarts. The issue is resolved in version 0.8.4-rc1 by applying appropriate rate limiters to the affected endpoint.
Affected products
- danny-avila LibreChat < 0.8.4-rc1
Timeline
- 2026-06-02: advisory: GitHub Security Advisory published
- 2026-06-25: disclosed: CVE published to NVD