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.
CVE-2026-59098
Score 6.5 from GitHub Security Advisory (severity: HIGH) published 2026-07-02. a secondary CVSS source baseline 6.5; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.5
- EG Score
- 6.5(high)
- EPSS
- 14.8%
- KEV
- Not listed
Published
July 2, 2026
Last Modified
July 6, 2026
Advisory Details (4)
Auto-updated Jul 7, 2026LobeHub 2.2.9 - Cross-User Document Disclosure via Unscoped RAG Semantic Search | Advisories | VulnCheck
https://www.vulncheck.com/advisories/lobechat-cross-user-document-disclosure-via-unscoped-rag-semantic-search🔒 fix(rag): scope knowledge-base file resolution to the caller
Fix merged in lobehub/lobehub PR #16594 on 2026-07-01 — awaiting tagged release
https://github.com/lobehub/lobehub/pull/16594Cross-user RAG document disclosure via unscoped semantic search (IDOR) · Issue #16535 · lobehub/lobehub · GitHub
https://github.com/lobehub/lobehub/issues/16535commit 4a7931a4e668 (lobehub/lobehub)
Fix landed in lobehub/lobehub commit 4a7931a4e668 — awaiting tagged release
https://github.com/lobehub/lobehub/commit/4a7931a4e66832947dba11afdffae2918a56b6a0Vendor Advisories for CVE-2026-59098(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 19× in last 7d / 19× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-07 03:44 UTCEG score recompute
- 2026-07-07 03:43 UTCGHSA enrichment
- 2026-07-06 16:41 UTCMITRE cvelistV5CVSS v4 → 7.1 · severity → MEDIUM
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-06 02:19 UTCEG score recompute
- 2026-07-06 02:19 UTCGHSA enrichment
- 2026-07-05 02:31 UTCEPSS rescore
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-05 00:54 UTCEG score recompute
- 2026-07-05 00:54 UTCGHSA enrichment
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-03 23:30 UTCEG score recompute
- 2026-07-03 23:30 UTCGHSA enrichment
- 2026-07-02 22:06 UTCEG score recompute
- 2026-07-02 22:06 UTCGHSA enrichment
Related CVEs(same CWE)
Same CWE
10 shownCWE-639
- CVE-2018-25270EG 9.8CRITICAL
- CVE-2017-20223EG 9.8CRITICAL
- CVE-2019-25487EG 9.8EPSS 94%CRITICAL
- CVE-2019-25235EG 9.8CRITICAL
- CVE-2020-16088EG 9.8CRITICAL
- CVE-2019-15310EG 9.8EPSS 94%CRITICAL
- CVE-2020-11658EG 9.8CRITICAL
- CVE-2019-15913EG 9.8CRITICAL
- CVE-2019-16340EG 9.8EPSS 97%CRITICAL
- CVE-2019-13360EG 9.8EPSS 98%CRITICAL
Frequently asked(5)
What is CVE-2026-59098?
When was CVE-2026-59098 disclosed?
Is CVE-2026-59098 actively exploited?
What is the CVSS score of CVE-2026-59098?
How do I remediate CVE-2026-59098?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-59098
Is Your Infrastructure Affected by CVE-2026-59098?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.