CVE-2026-54039
High 8.1No known exploitationFix status unknownTitle not yet published
Record last updated
CVSS score
High on a 0 to 10 scale
EPSS, chance of exploitation in 30 days
No EPSS score available
CISA remediation deadline
Not in the KEV catalog
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.
Weakness: CWE-287, CWE-915
Patching and mitigation
- Patch status
- Unknown: no source documents a fix
- Mitigation
- None documented
- Vendor guidance
- No vendor link on record
Affected products
No affected products documented yet.
Timeline
- No dated events documented yet.
Vendor guidance and references
- https://github.com/LibreChat-AI/LibreChat/commit/b01d34abe29152e6e7f763089c0d9a6e647d0dba (opens in a new tab)
- https://github.com/LibreChat-AI/LibreChat/pull/13307 (opens in a new tab)
- https://github.com/LibreChat-AI/LibreChat/releases/tag/v0.8.6 (opens in a new tab)
- https://github.com/LibreChat-AI/LibreChat/security/advisories/GHSA-wjpf-x42h-cv4m (opens in a new tab)
- https://www.librechat.ai/changelog/v0.8.6 (opens in a new tab)