Is there a public PoC exploit available for CVE-2026-59100?

Yes, a public proof-of-concept exploit is available for CVE-2026-59100. Prioritise patching immediately. EPSS: 0.2%.

Is there a patch available for CVE-2026-59100?

Yes, a patch is available for CVE-2026-59100. Update the affected software to the latest version immediately.

LobeChat CVE-2026-59100

Q: What is the CVSS score of CVE-2026-59100?

CVE-2026-59100 has a CVSS 4.0 base score of 2.3 (Low). CVSS vector: CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. EPSS exploitation probability: 0.2%.

EUVD-2026-41431 LOW

Authorization Bypass Through User-Controlled Key (CWE-639)

2026-07-02 VulnCheck

GHSA-hgpq-q5hf-7r77

Authentication Bypass Lobehub

2.3

CVSS 4.0 · Vendor: VulnCheck

Severity by source

Vendor (VulnCheck) PRIMARY

2.3 MEDIUM

CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

vuln.today AI

5.0 MEDIUM

Network-reachable BOLA requiring group ID enumeration (AC:H); authenticated low-privilege session (PR:L); limited read, write, and disruptive impact on user data only with no scope change (C:L/I:L/A:L, S:U).

3.1 AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L

4.0 AV:N/AC:H/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N

Primary rating from Vendor (VulnCheck).

CVSS VectorVendor: VulnCheck

Attack Vector

Network

Attack Complexity

High

Privileges Required

Low

User Interaction

None

Scope

Lifecycle Timeline

Analysis Generated

Jul 02, 2026 - 20:39 vuln.today

Severity Changed

Jul 02, 2026 - 20:22 NVD

MEDIUM LOW

CVSS changed

Jul 02, 2026 - 20:22 NVD

5.0 (MEDIUM) 2.3 (LOW)

DescriptionCVE.org

LobeChat through 2.2.9 contains a broken object level authorization vulnerability that allows authenticated attackers to access and modify other users' chat-group agent data by supplying arbitrary group identifiers. Attackers can invoke the getGroupAgents, updateAgentInGroup, and removeAgentsFromGroup operations without user-scoped predicates to read agent listings, modify agent roles and ordering, and remove agents from chat groups belonging to other users.

AnalysisAI

Broken object level authorization in LobeChat through version 2.2.9 permits authenticated users to read and manipulate chat-group agent data belonging to other users by supplying arbitrary group identifiers to unguarded API operations. The getGroupAgents, updateAgentInGroup, and removeAgentsFromGroup endpoints accept caller-controlled group IDs without validating ownership, enabling cross-user data access and modification. Publicly available exploit code exists per GitHub issue #16537, though the CVE is absent from the CISA KEV catalog and carries a CVSS 4.0 score of 2.3, indicating limited blast radius; real-world risk is elevated primarily in shared multi-tenant LobeChat deployments.

Technical ContextAI

LobeChat is an open-source AI chat framework developed by LobeHub, identified by CPE cpe:2.3:a:lobehub:lobehub:*:*:*:*:*:*:*:*. The root cause is CWE-639 (Authorization Bypass Through User-Controlled Key), a class of Broken Object Level Authorization (BOLA) flaw - a well-known OWASP API Security Top 10 category - where API endpoints accept user-supplied resource identifiers without enforcing ownership or access-control predicates scoped to the requesting user's identity. The three affected operations (getGroupAgents, updateAgentInGroup, removeAgentsFromGroup) retrieve and mutate chat-group agent records based solely on the caller-supplied group ID, with no server-side check that the authenticated session's user owns or has permission to access that group. This is a design-level authorization omission rather than a memory-safety or injection flaw.

RemediationAI

An upstream fix has been committed to the LobeHub repository via commit 9ed5a7e20d8a67c431265f5a252e9559d9920907 (https://github.com/lobehub/lobehub/commit/9ed5a7e20d8a67c431265f5a252e9559d9920907) and merged through pull request #16586 (https://github.com/lobehub/lobehub/pull/16586); however, a specific tagged release version incorporating this fix is not independently confirmed from available data - operators should monitor the LobeHub release page for a version beyond 2.2.9 that includes this commit. As a compensating control prior to patching in shared deployments, restrict API access to the affected group-agent endpoints (getGroupAgents, updateAgentInGroup, removeAgentsFromGroup) via network-layer controls or reverse-proxy ACLs to authenticated internal users only - note this does not eliminate the flaw for insider threat scenarios. Additionally, audit API access logs for anomalous cross-user group identifier patterns as a detection measure. Single-user or isolated LobeChat instances face no meaningful exploitation risk from this vulnerability.