Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-23522: CWE-284: Improper Access Control in lobehub lobe-chat

0
Low
Published: Mon Jan 19 2026 (01/19/2026, 16:53:32 UTC)
Source: CVE Database V5
Vendor/Project: lobehub
Product: lobe-chat

Description

LobeChat is an open source chat application platform. Prior to version 2.0.0-next.193, `knowledgeBase.removeFilesFromKnowledgeBase` tRPC ep allows authenticated users to delete files from any knowledge base without verifying ownership. `userId` filter in the database query is commented out, so it's enabling attackers to delete other users' KB files if they know the knowledge base ID and file ID. While the vulnerability is confirmed, practical exploitation requires knowing target's KB ID and target's file ID. These IDs are random and not easily enumerable. However, IDs may leak through shared links, logs, referrer headers and so on. Missing authorization check is a critical security flaw regardless. Users should upgrade to version 2.0.0-next.193 to receive a patch.

AI-Powered Analysis

AILast updated: 01/26/2026, 19:48:30 UTC

Technical Analysis

CVE-2026-23522 is a security vulnerability classified under CWE-284 (Improper Access Control) affecting lobe-chat, an open source chat application platform. The flaw exists in the tRPC endpoint `knowledgeBase.removeFilesFromKnowledgeBase` prior to version 2.0.0-next.193. This endpoint allows authenticated users to delete files from any knowledge base without verifying if the user owns or has permission to modify that knowledge base. The root cause is a commented-out `userId` filter in the database query responsible for enforcing ownership checks. Consequently, an attacker who is authenticated can delete files belonging to other users if they know the knowledge base ID and the file ID. These IDs are randomly generated and not easily guessable or enumerable, which raises the attack complexity. However, these identifiers may leak through shared links, logs, or HTTP referrer headers, increasing the risk of exploitation. The vulnerability affects data integrity by enabling unauthorized deletion of files but does not impact confidentiality or availability. No public exploits have been reported yet. The vendor has addressed the issue in version 2.0.0-next.193 by restoring proper authorization checks. The CVSS v3.1 base score is 3.7, reflecting a low severity mainly due to the high attack complexity and limited impact scope.

Potential Impact

For European organizations using lobe-chat versions prior to 2.0.0-next.193, this vulnerability poses a risk to data integrity within knowledge bases. Unauthorized deletion of files could disrupt collaboration, cause data loss, and impact business processes relying on shared knowledge. Although the vulnerability does not directly affect confidentiality or availability, the loss of critical knowledge base files could indirectly affect operational continuity and decision-making. The requirement for authentication limits exposure to internal or compromised users, but leaked knowledge base and file IDs could enable targeted attacks. Organizations in sectors with stringent data integrity requirements, such as finance, healthcare, and government, may face increased risk. The absence of known exploits reduces immediate threat but patching is essential to prevent potential abuse, especially in environments where knowledge base links or logs are widely shared or insufficiently protected.

Mitigation Recommendations

European organizations should immediately upgrade lobe-chat to version 2.0.0-next.193 or later to ensure the authorization checks are properly enforced. In addition to patching, organizations should audit access logs and knowledge base sharing practices to identify potential leakage of knowledge base and file IDs. Implement strict access controls and monitoring on knowledge base sharing links and logs to minimize ID exposure. Employ network segmentation and role-based access controls to restrict authenticated users’ permissions to only their own knowledge bases. Regularly review and update authentication and authorization mechanisms within the platform. Educate users about the risks of sharing knowledge base links publicly or in unsecured channels. Consider implementing additional logging and alerting for unusual deletion activities. Finally, integrate vulnerability management processes to track and remediate such flaws promptly.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-01-13T18:22:43.980Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 696e7feca027839b3dc01196

Added to database: 1/19/2026, 7:03:08 PM

Last enriched: 1/26/2026, 7:48:30 PM

Last updated: 2/7/2026, 6:45:00 PM

Views: 65

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats