Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Primary rating from GitHub Advisory · only source for this CVE.
CVSS VectorGitHub Advisory
Lifecycle Timeline
4DescriptionGitHub Advisory
LibreChat is a ChatGPT clone with additional features. Prior to 0.8.3-rc1, a Denial of Service (DoS) vulnerability exists in the DELETE /api/convos endpoint that allows an authenticated attacker to crash the Node.js server process by sending malformed requests. The DELETE /api/convos route handler attempts to destructure req.body.arg without validating that it exists. The server crashes due to an unhandled TypeError that bypasses Express error handling middleware and triggers process.exit(1). This vulnerability is fixed in 0.8.3-rc1.
AnalysisAI
LibreChat versions prior to 0.8.3-rc1 contain a Denial of Service vulnerability in the DELETE /api/convos endpoint where authenticated attackers can crash the Node.js server process by sending malformed requests lacking the required req.body.arg parameter. The vulnerability exploits improper destructuring without validation, causing an unhandled TypeError that bypasses Express middleware and triggers process.exit(1), resulting in complete service unavailability. No evidence of active exploitation in the wild or public POC has been identified at this time.
Technical ContextAI
LibreChat is a Node.js-based ChatGPT clone application (CPE: cpe:2.3:a:danny-avila:librechat). The vulnerability stems from CWE-248 (Uncaught Exception), a root cause class involving improper exception handling. Specifically, the DELETE /api/convos route handler performs destructuring assignment on req.body.arg without prior null/undefined validation. When a malformed request omits this parameter, JavaScript throws a TypeError during destructuring, which is not caught by the route handler or Express error middleware, causing the entire Node.js process to terminate. This indicates a lack of defensive programming practices and insufficient input validation at the route handler level before object destructuring operations.
RemediationAI
Immediate patch: Upgrade LibreChat to version 0.8.3-rc1 or later once released as stable. For users unable to patch immediately: (1) Implement network-level access controls restricting who can authenticate to LibreChat instances (e.g., VPN, allowlisting); (2) Deploy a reverse proxy (nginx, HAProxy) with request body validation rules that reject requests to DELETE /api/convos lacking the 'arg' parameter; (3) Monitor Node.js process logs for unexpected exits and implement auto-restart policies (systemd, PM2, Docker restart policies) to reduce downtime impact; (4) Implement rate limiting on authenticated users to slow attack velocity. Code-level workaround (if patching is delayed): Add input validation middleware before the DELETE /api/convos handler to validate req.body.arg existence and type before destructuring.
A vulnerability in the NuPoint Unified Messaging (NPM) component of Mitel MiCollab through 9.8 SP1 FP2 (9.8.1.201) could
FortiOS and FortiProxy contain an authentication bypass via the Node.js websocket module allowing unauthenticated remote
Denial of service against HTTP/2 server implementations allows remote unauthenticated attackers to exhaust server resour
Eval injection vulnerability in the internals.batch function in lib/batch.js in the bassmaster plugin before 1.5.2 for t
Flowise version 3.0.5 contains a remote code execution vulnerability in the CustomMCP node. The mcpServerConfig paramete
Node.js 8.5.0 before 8.6.0 allows remote attackers to access unintended files, because a change to ".." handling was inc
An issue was discovered in the node-serialize package 0.0.4 for Node.js. Rated critical severity (CVSS 9.8), this vulner
OpenSSL before 0.9.8za, 1.0.0 before 1.0.0m, and 1.0.1 before 1.0.1h does not properly restrict processing of ChangeCiph
Directory traversal vulnerability in the st module before 0.2.5 for Node.js allows remote attackers to read arbitrary fi
Multiple SQL injection vulnerabilities in the Manage Accounts page in the AccountManagement.asmx service in the Solarwin
The JS-YAML module before 2.0.5 for Node.js parses input without properly considering the unsafe !!js/function tag, whic
The AES-NI implementation in OpenSSL before 1.0.1t and 1.0.2 before 1.0.2h does not consider memory allocation during a
Same weakness CWE-248 – Uncaught Exception
View allSame technique Denial Of Service
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-12093