CVE-2026-54039
LibreChat authentication bypass
- Published20 Nov 2026
Description
LibreChat is an enhanced ChatGPT clone that supports multiple AI providers. From 0.7.0 until 0.8.6, when local registration is enabled and at least one social provider is configured, POST /api/auth/register passes an unparsed request object into api/server/services/AuthService.js, allowing an unauthenticated attacker to persist a forged provider value for a known victim email. The api/strategies/socialLogin.js email-fallback path then accepts the planted record when the victim signs in because it compares the stored provider name without requiring the provider subject identifier. The victim OAuth session and the attacker local-password session become bound to the same user record, giving the attacker persistent read and write access to data created by the victim. The first-user administrator role is an additional conditional impact only on a fresh deployment. This issue is fixed in version 0.8.6.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:NRemediation
No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.
References
- https://github.com/LibreChat-AI/LibreChat/commit/b01d34abe29152e6e7f763089c0d9a6e647d0dba
- https://github.com/LibreChat-AI/LibreChat/pull/13307
- https://github.com/LibreChat-AI/LibreChat/releases/tag/v0.8.6
- https://github.com/LibreChat-AI/LibreChat/security/advisories/GHSA-wjpf-x42h-cv4m
- https://www.librechat.ai/changelog/v0.8.6
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2026-54039 being actively exploited?
CVE-2026-54039 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.67%.
How severe is CVE-2026-54039?
CVE-2026-54039 has a CVSS 3.1 base score of 8.1, rated high. EPSS estimates a 0.67% probability of exploitation.
How do I fix CVE-2026-54039?
Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-54039 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. The CVSS 4.0 base score is shown where the NVD has one, otherwise CVSS 3.1.