LibreChat-AI LibreChat up to 0.8.8 Regex Query Construction userGroup.ts findGroupsByNamePattern/searchPrincipals q incorrect regex
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00+ |
Summary
A vulnerability marked as problematic has been reported in LibreChat-AI LibreChat up to 0.8.8. This affects the function findGroupsByNamePattern/searchPrincipals of the file packages/data-schemas/src/methods/userGroup.ts of the component Regex Query Construction. The manipulation of the argument q leads to incorrect regex.
This vulnerability is documented as CVE-2026-54038. The attack can be initiated remotely. There is not any exploit available.
It is suggested to upgrade the affected component.
Details
A vulnerability, which was classified as problematic, has been found in LibreChat-AI LibreChat up to 0.8.8. This issue affects the function findGroupsByNamePattern/searchPrincipals of the file packages/data-schemas/src/methods/userGroup.ts of the component Regex Query Construction. The manipulation of the argument q with an unknown input leads to a incorrect regex vulnerability. Using CWE to declare the problem leads to CWE-185. The product specifies a regular expression in a way that causes data to be improperly matched or compared. Impacted is availability. The summary by CVE is:
LibreChat is an enhanced ChatGPT clone that supports multiple AI providers. Prior to 0.8.9, GET /api/permissions/search-principals passes the q parameter to JavaScript RegExp construction and MongoDB regex queries in packages/data-schemas/src/methods/userGroup.ts findGroupsByNamePattern and searchPrincipals without escaping metacharacters. An authenticated user with people-picker permission can submit a catastrophic-backtracking pattern that blocks the Node.js event loop and makes the service unresponsive to concurrent users; invalid patterns can also produce server errors. This issue is fixed in version 0.8.9.
The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-54038 since 06/11/2026. The exploitation is known to be easy. The attack may be initiated remotely. Technical details are known, but no exploit is available.
Upgrading to version 0.8.9 eliminates this vulnerability.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.4VulDB Meta Temp Score: 5.3
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 6.5
CNA Vector (GitHub_M): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Incorrect regexCWE: CWE-185 / CWE-697
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: LibreChat 0.8.9
Timeline
06/11/2026 CVE reserved11/20/2026 Advisory disclosed
11/20/2026 VulDB entry created
11/20/2026 VulDB entry last update
Sources
Product: github.comAdvisory: github.com
Status: Confirmed
CNA: GitHub_M
CVE: CVE-2026-54038 (🔒)
GCVE (CVE): GCVE-0-2026-54038
GCVE (VulDB): GCVE-100-441641
Entry
Created: 11/20/2026 21:31Changes: 11/20/2026 21:31 (68)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.