What is the CVSS score of CVE-2025-41258?

CVE-2025-41258 has a CVSS 3.1 base score of 8.0 (High). CVSS vector: CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. EPSS exploitation probability: 0.0%.

Which versions of Librechat are affected by CVE-2025-41258?

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…

How to fix or mitigate CVE-2025-41258?

Within 24 hours: Identify all LibreChat 0.8.1-rc2 instances in production and isolate them from untrusted networks; disable RAG API functionality if not business-critical. Within 7 days: Implement network segmentation to restrict RAG API access to trusted hosts only; conduct audit of RAG API access logs for unauthorized activity. Within 30 days: Upgrade to a patched version when available; if upgrade unavailable, implement a Web Application Firewall with rules to segregate JWT validation logic between session and RAG endpoints, or retire the affected version.

Librechat CVE-2025-41258

EUVD-2025-208825 HIGH

Improper Access Control (CWE-284)

2026-03-18 sba-research

Authentication Bypass Librechat

8.0

CVSS 3.1 · NVD

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

CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector

Adjacent

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

EUVD ID Assigned

Mar 18, 2026 - 11:30 euvd

EUVD-2025-208825

Analysis Generated

Mar 18, 2026 - 11:30 vuln.today

CVE Published

Mar 18, 2026 - 11:08 nvd

HIGH 8.0

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.

AnalysisAI

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.

Technical ContextAI

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.

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.