Skip to main content

LobeChat CVE-2026-59098

| EUVDEUVD-2026-41429 HIGH
Authorization Bypass Through User-Controlled Key (CWE-639)
2026-07-02 VulnCheck GHSA-w676-mrp6-5fqq
7.1
CVSS 4.0 · Vendor: VulnCheck
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Register or obtain low-privilege account
  2. Delivery
    Authenticate to LobeChat instance
  3. Exploit
    Call chunk retrieval / chat knowledge-base endpoint
  4. Execution
    Supply victim file or KB identifiers
  5. Persist
    Unscoped semanticSearch returns cross-user chunks
  6. Impact
    Exfiltrate other users' documents and metadata

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Object-level authorization, IDOR prevention
Exploitation Conditions

Exploitation requires a valid authenticated LobeChat account (PR:L) and a target instance running version 2.2.9 or earlier that hosts other users' RAG data - i.e., a multi-tenant or shared deployment with populated knowledge bases. The attacker must reach the chunk-retrieval or chat knowledge-base API paths over the network and supply victim-owned file or knowledge-base identifiers; no user interaction or elevated privileges are needed. Limiting factors: single-user/self-hosted instances with no other tenants have nothing to disclose, and deployments that disable public registration make obtaining the required low-privilege account harder, meaningfully reducing real-world exposure despite the network attack vector.

Impact

The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N) scores 7.1 and describes a network-reachable, low-complexity attack requiring only low-privilege authentication (any valid account), with high confidentiality impact and no integrity or availability impact - an accurate profile for an IDOR-style data-disclosure bug. Publicly available exploit code raises practical risk, and the issue was reported by VulnCheck with a corresponding upstream fix, so exploitation is straightforward for anyone with an account on an affected instance. Countervailing factors: it is NOT in CISA KEV, no active exploitation is reported, and no EPSS score was provided, so realistic risk is 'reliably exploitable but not yet weaponized at scale.' The main limiter is the PR:L requirement - impact is highest on multi-tenant or publicly-registrable LobeChat deployments and negligible on single-user instances.

Exploit ScenarioDerived

An attacker registers or already holds a low-privilege account on a shared LobeChat instance, then issues chunk-retrieval or chat knowledge-base requests substituting another user's file or knowledge-base identifiers. Because the semanticSearch query lacks a user-scope filter, the server returns the victim's document text, file names, and metadata. Publicly available exploit code makes this repeatable, and the low attack complexity means no timing or special tooling is required.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.2% exploitation probability (EPSS)

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

Alert me

AnalysisAIv1 – Jul 02, 2026

Cross-user data disclosure in LobeChat through version 2.2.9 allows any authenticated user to read other users' documents by abusing the retrieval-augmented-generation (RAG) semantic search, whose chunk model omits a user-identifier predicate. By supplying arbitrary victim file or knowledge-base identifiers through the chunk retrieval and chat knowledge-base paths, an attacker recovers text content, file names, and metadata belonging to other tenants. Publicly available exploit code exists and a vendor patch has been released; the flaw is not listed in CISA KEV and no active exploitation is reported.

RemediationAI

Patch available per vendor advisory: upgrade to the fixed LobeChat release that includes commit 4a7931a4e66832947dba11afdffae2918a56b6a0 (merged via PR https://github.com/lobehub/lobehub/pull/16594); a specific tagged patched version number is not stated in the provided data, so confirm the exact release with the vendor before deploying. If immediate patching is not possible, compensating controls include restricting instance access to trusted users only (disable open/self-service registration so PR:L cannot be trivially satisfied), placing the instance behind an authenticating reverse proxy or VPN, and temporarily disabling or not populating shared knowledge-base/RAG features so no cross-user documents are exposed - the trade-off being loss of RAG functionality for all users. Monitor chunk-retrieval and knowledge-base endpoints for requests referencing file or knowledge-base identifiers the account does not own. See the VulnCheck advisory and GitHub issue 16535 for details.

Affected VersionsENISA

lobehub 0 ≤2.2.9

Affected Packages

euvd lobehub 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

LobeChat (lobehub) is an open-source AI chat framework that supports knowledge bases and RAG, where uploaded files are split into chunks, embedded, and retrieved by vector/semantic similarity to ground model responses. The root cause is CWE-639 (Authorization Bypass Through User-Controlled Key): the chunk model's semanticSearch method performs similarity lookups without scoping the query to the requesting user's identifier, so ownership is never enforced at the data layer. Because the file/knowledge-base identifiers are attacker-controllable and no user predicate filters the result set, the query returns chunks across the entire multi-tenant store. Affected code is identified by CPE cpe:2.3:a:lobehub:lobehub covering all versions up to and including 2.2.9.

Know when Lobehub 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

Vendor (VulnCheck) PRIMARY 7.1 MEDIUM
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
vuln.today AI 6.5 MEDIUM

Network-reachable RAG endpoint, only a low-privilege account needed (PR:L), no user interaction; impact is confidentiality-only cross-user disclosure with no integrity or availability effect.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (VulnCheck).

CVSS VectorVendor: VulnCheck

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
Low
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
None
Vulnerable system: Availability
None
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

2
Severity Changed
Jul 02, 2026 - 20:22 NVD
MEDIUM HIGH
CVSS changed
Jul 02, 2026 - 20:22 NVD
6.5 (MEDIUM) 7.1 (HIGH)

DescriptionCVE.org

LobeChat through 2.2.9 contains a broken access control vulnerability in the retrieval-augmented-generation semantic search functionality that allows authenticated attackers to access other users' data by exploiting missing user-identifier predicates in the chunk model semanticSearch method. Attackers can supply arbitrary victim file or knowledge-base identifiers through the chunk retrieval and chat knowledge-base paths to retrieve text content, file names, and metadata belonging to other users.

Executive ViewAI

Why It Matters

LobeChat versions through 2.2.9 contain a cross-user data disclosure vulnerability enabling any authenticated user to access documents, file names, and metadata belonging to other users in multi-tenant deployments. The vulnerability exploits a missing access control in the semantic search function, creating a confidentiality breach across all system users. With publicly available exploit code and broad accessibility to all authenticated users, this demands immediate remediation to prevent unauthorized data exposure and regulatory violations.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.2%
Top 85% exploitable
Prevalence
Low
open-source self-hosted AI chat app, niche footprint versus enterprise software
Exploit
POC
Public exploit code exists
Data Quality
7 sources
Confidence: High
EUVD NVD CVE.org EPSS Vulnrichment GitHub VulDB

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 Yes
EPSS 0.2%
Patch available Yes
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
Scheduled
Exploitation
Poc
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Partial

Priority Score

56
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +36
PoC: +20
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.

CVE-2024-32964 CRITICAL POC
9.0 May 14

Lobe Chat is a chatbot framework that supports speech synthesis, multimodal, and extensible Function Call plugin system.

CVE-2024-47066 HIGH POC
8.8 Sep 23

Lobe Chat is an open-source artificial intelligence chat framework. Rated high severity (CVSS 8.8), this vulnerability i

CVE-2024-32965 HIGH POC
8.6 Nov 26

Lobe Chat is an open-source, AI chat framework. Rated high severity (CVSS 8.6), this vulnerability is remotely exploitab

CVE-2026-59095 HIGH POC
8.3 Jul 02

Server-side request forgery in LobeChat before 2.2.10-canary.18 lets authenticated users coerce the server into issuing

CVE-2026-58578 HIGH POC
7.1 Jul 02

Denial of service in LobeChat before 2.2.10-canary.15 lets an authenticated user hang the entire Node.js server by impor

CVE-2024-37895 MEDIUM POC
5.7 Jun 17

Lobe Chat is an open-source LLMs/AI chat framework. Rated medium severity (CVSS 5.7), this vulnerability is remotely exp

CVE-2024-24566 MEDIUM POC
5.3 Jan 31

Lobe Chat is a chatbot framework that supports speech synthesis, multimodal, and extensible Function Call plugin system.

CVE-2026-120315 HIGH
8.7 Nov 02

Path traversal in LobeHub Chat (npm @lobehub/chat, versions 1.84.26 through 2.1.48) lets any authenticated user write ar

CVE-2025-59426 MEDIUM POC
4.3 Sep 25

Lobe Chat is an open-source artificial intelligence chat framework. Rated medium severity (CVSS 4.3), this vulnerability

CVE-2026-72594 HIGH
7.6 Aug 10

Stored XSS in lobehub/lobe-chat through v2.2.13 allows a low-privileged authenticated user to persist malicious JavaScri

CVE-2026-85621 MEDIUM
6.9 Sep 04

Webhook signature verification bypass in LobeChat 2.2.1 allows unauthenticated remote attackers to inject forged inbound

CVE-2026-59100 LOW POC
2.3 Jul 02

Broken object level authorization in LobeChat through version 2.2.9 permits authenticated users to read and manipulate c

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