Skip to main content

Librechat EUVDEUVD-2025-208825

| CVE-2025-41258 HIGH
Improper Access Control (CWE-284)
2026-03-18 sba-research
8.0
CVSS 3.1 · NVD
View

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Access control enforcement
MITRE ATT&CK

1 technique across 1 tactic: Defense Evasion

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Impact

The CVSS score of 8.0 (High) reflects the vulnerability's significant impact with adjacent network attack vector (AV:A), low complexity (AC:L), and requiring only low privileges (PR:L). The attack enables high confidentiality, integrity, and availability impact (C:H/I:H/A:H) without user interaction. However, real-world risk is tempered by several factors: the attack requires adjacent network access and authenticated user credentials, limiting the attack surface compared to remote unauthenticated exploits. The vulnerability affects a specific release candidate version (0.8.1-rc2) rather than a stable production release, potentially reducing the number of deployed instances. While the technical impact is severe for affected installations allowing lateral movement from user sessions to RAG API access, the adjacent network requirement and authentication prerequisite make this less immediately critical than remotely exploitable unauthenticated vulnerabilities, though it remains a serious concern for multi-tenant or shared hosting environments.

Exploit ScenarioDerived

An authenticated user with low-privilege access to LibreChat on an adjacent network obtains their own session JWT token through normal authentication. By analyzing the token structure and reusing the same JWT secret that signs both user sessions and RAG API requests, the attacker crafts or repurposes their session token to authenticate directly to the RAG API endpoints, bypassing service-level access controls. This allows the attacker to read sensitive RAG data, modify retrieval configurations, or disrupt the RAG service availability, potentially accessing other users' context data or poisoning the knowledge base used for AI-augmented responses across the application.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Mar 18, 2026

A critical authentication bypass vulnerability exists in LibreChat version 0.8.1-rc2 where the same JWT secret is reused for both user session management and the RAG (Retrieval-Augmented Generation) API authentication. This design flaw allows authenticated users to compromise service-level authentication of the RAG API by leveraging their session tokens to access or manipulate the RAG service beyond intended privileges. No active exploitation (KEV) has been reported, but a detailed security advisory with technical analysis is publicly available from SBA Research.

RemediationAI

Users running LibreChat version 0.8.1-rc2 should immediately upgrade to a patched version or implement separate JWT secrets for user session management and RAG API authentication by modifying the application configuration to use distinct cryptographic keys for each authentication domain. Review the SBA Research security advisory at https://github.com/sbaresearch/advisories/tree/public/2025/SBA-ADV-20251205-01_LibreChat_RAG_API_Authentication_Bypass for detailed technical guidance and consult the official LibreChat repository at https://github.com/danny-avila/LibreChat for patch availability and upgrade instructions. As an interim mitigation, restrict network access to the RAG API endpoints to only trusted service accounts and implement additional authorization checks to validate that JWT tokens used for RAG API access originate from legitimate service contexts rather than user sessions.

Affected VersionsENISA

LibreChat 0.8.1-rc2

Affected Packages

euvd librechat no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

LibreChat is a web-based chat application (cpe:2.3:a:danny-avila:librechat) that implements RAG (Retrieval-Augmented Generation) functionality for enhanced AI responses. The vulnerability stems from CWE-284 (Improper Access Control) where the application uses a shared JWT signing secret across different security boundaries. When the same cryptographic key material is used to sign tokens for user sessions and service-level API authentication, users can potentially forge or reuse their session JWTs to authenticate to backend services that should have separate authentication mechanisms. This violates the principle of defense in depth and breaks service isolation.

Know when Librechat gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

NVD PRIMARY 8.0 HIGH
AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

Attack Vector
Adjacent
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

DescriptionCVE.org

LibreChat version 0.8.1-rc2 uses the same JWT secret for the user session mechanism and RAG API which compromises the service-level authentication of the RAG API.

Executive ViewAI

Why It Matters

LibreChat version 0.8.1-rc2 contains a critical authentication bypass that allows low-privilege users to gain unauthorized administrative access to RAG API functionality, potentially exposing sensitive data and enabling service manipulation. Any organization running this version with internet or adjacent network exposure faces immediate risk of data breach and system compromise.

Business Impact: Severe
Compensating Controls

Implement strict network segmentation restricting RAG API access to trusted internal networks only; deploy Web Application Firewall rules to enforce separate authentication mechanisms or tokens for RAG API distinct from session JWTs; disable RAG functionality entirely if business operations permit; implement enhanced API monitoring and alerting for RAG endpoint access patterns; require multi-factor authentication for administrative functions; rotate all JWT secrets immediately and monitor for unauthorized token generation.

Threat Intelligence Overview

EPSS Score
0.0%
Top 91% exploitable
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.0%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Controlled
Automatable· derived
No
Human Impact
Very High

Priority Score

40
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +40
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

Related Vulnerabilities in LibreChat JWT and Authorization Flaws

View all 2
CVE-2024-11170 HIGH POC
8.8 Mar 20

A vulnerability in danny-avila/librechat version git 81f2936 allows for path traversal due to improper sanitization of f

CVE-2024-10361 CRITICAL POC
9.1 Mar 20

An arbitrary file deletion vulnerability exists in danny-avila/librechat version v0.7.5-rc2, specifically within the /ap

CVE-2026-22252 CRITICAL POC
9.1 Jan 12

LibreChat before v0.8.2-rc2 allows any authenticated user to execute shell commands as root inside the container through

CVE-2025-8850 HIGH POC
8.8 Oct 30

LibreChat 0.7.9 lets an authenticated user turn off two-factor authentication on their own account without supplying a v

CVE-2025-66450 HIGH POC
8.6 Dec 11

Stored cross-site scripting and tracker injection in LibreChat 0.8.0 and earlier allow a user who can create a chat to c

CVE-2025-66201 HIGH POC
8.6 Nov 29

LibreChat is a ChatGPT clone with additional features. Rated high severity (CVSS 8.6), this vulnerability is remotely ex

CVE-2025-69222 HIGH POC
8.1 Jan 07

LibreChat 0.8.1-rc2 has SSRF in the Actions feature that allows authenticated users to make the server perform requests

CVE-2024-11171 HIGH POC
7.5 Mar 20

In danny-avila/librechat version git 0c2a583, there is an improper input validation vulnerability. Rated high severity (

CVE-2025-7104 HIGH POC
7.5 Sep 29

A mass assignment vulnerability exists in danny-avila/librechat, affecting all versions. Rated high severity (CVSS 7.5),

CVE-2025-8849 HIGH POC
7.5 Oct 31

Unbounded `key` and `value` parameters on the LibreChat 0.7.9 memory API (`POST /api/memories` and `PATCH /api/memories/

CVE-2024-11173 MEDIUM POC
6.5 Mar 20

An unhandled exception in the danny-avila/librechat repository, version git 600d217, can cause the server to crash, lead

CVE-2024-10366 MEDIUM POC
6.5 Mar 20

An improper access control vulnerability (IDOR) exists in the delete attachments functionality of danny-avila/librechat

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy