All vulnerabilities

Servers and applications

GHSA-qr96-j5w9-44gf

Two-factor authentication: TOTP shared secret and backup codes below recommended entropy

Severity
Medium
Published
17 Nov 2026
Last changed
17 Nov 2026
Added to UpHeron
17 Nov 2026
Fixed in
0.8.9
Weakness
CWE-331CWE-759
Sources
Project advisories (GitHub)

Description

Two entropy issues in LibreChat's two-factor authentication, both present in stock configuration with no operator opt-in, in api/server/services/twoFactorService.js.

  • The TOTP shared secret is derived from 10 random bytes (80 bits). RFC 4226 §4 R6 states the shared secret MUST be at least 128 bits and RECOMMENDS 160. RFC 6238 inherits this for TOTP.
  • Backup codes are derived from 4 random bytes (32 bits) and stored as unsalted SHA-256. A 32-bit space under a single unsalted hash is precomputable once and reusable against every LibreChat instance, so anyone who obtains the user collection recovers working second factors rather than hashes.

The second finding is the one we would weight. Backup codes are account-recovery credentials that bypass the TOTP factor, and unlike the TOTP secret they are not encrypted at rest — a hash is treated as sufficient protection, and at 32 bits unsalted it is not.

From LibreChat-AI/LibreChat's security advisory. Shortened; the full text is there.

Affected software

SoftwareAffected versions
LibreChatServers and applications · github:librechat-ai/librechat
  • Every version before 0.8.9

About LibreChat

Enhanced ChatGPT Clone: Features Agents, MCP, Skills, DeepSeek, Anthropic, AWS, OpenAI, Responses API, Azure, Groq, o1, GPT-5, Mistral, OpenRouter, Vertex AI, Gemini, Artifacts, AI model switching, message search, Code Interpreter, langchain, DALL-E-3, OpenAPI Actions, Functions, Secure Multi-User Auth, Presets, open-source for self-hosting. Active

From its GitHub repository.
Docker Hub pulls
669,094Docker Hub, 15 Nov 2026
GitHub stars
47,138GitHub, 15 Nov 2026
Forks
9,706GitHub, 15 Nov 2026
License
MITGitHub
First published on GitHub
12 Feb 2023GitHub

References