LobeChat through 2.2.9 server-database deployments are vulnerable to broken object-level authorization in MessageModel. The updateMessagePlugin, updatePluginState, updatePluginError, updateTTS and updateTranslate methods filter target rows by message id alone, omitting the userId scope that sibling methods apply, and findMessagePlugin reads back by id alone. Reachable via the corresponding tRPC message procedures, an authenticated user who knows another user's message identifier can overwrite that victim's plugin tool-call metadata, plugin state/error, text-to-speech and translation records on the same instance, and the tampered content is served back to the victim. Exploitation requires knowledge of the victim's non-enumerable message identifier.
CVE-2026-58580
Score 5.9 from GitHub Security Advisory published 2026-07-02. the CNA's CVSS baseline 5.9; 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
- 5.9
- EG Score
- 5.9(high)
- EPSS
- 5.0%
- KEV
- Not listed
Published
July 2, 2026
Last Modified
July 6, 2026
References (3)
- disclosure@vulncheckhttps://github.com/lobehub/lobehub/issues/16534
- disclosure@vulncheckhttps://www.vulncheck.com/advisories/lobechat-broken-object-level-authorization-in-message-sub-resource-writes
- 134c704f-9b21-4f2e-91b3-4a467353bcc0https://github.com/lobehub/lobehub/issues/16534
Vendor Advisories for CVE-2026-58580(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-06 16:43 UTCEG score recompute
- 2026-07-06 16:43 UTCGHSA enrichment
- 2026-07-06 16:41 UTCMITRE cvelistV5CVSS v4 → 6
- 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-05 18:05 UTCEG score recompute
- 2026-07-05 18:05 UTCGHSA enrichment
- 2026-07-05 02:31 UTCEPSS rescore
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-04 19:25 UTCEG score recompute
- 2026-07-04 19:25 UTCGHSA enrichment
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-03 20:47 UTCEG score recompute
- 2026-07-03 20:46 UTCGHSA enrichment
- 2026-07-02 22:07 UTCEG score recompute
- 2026-07-02 22:07 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-58580?
When was CVE-2026-58580 disclosed?
Is CVE-2026-58580 actively exploited?
What is the CVSS score of CVE-2026-58580?
How do I remediate CVE-2026-58580?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-58580
Is Your Infrastructure Affected by CVE-2026-58580?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.