Quick answers
- Is CVE-2026-58580 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-58580 being exploited in the wild.
- How severe is CVE-2026-58580?
- Medium severity, with a CVSS score of 5.9, published 2 July 2026.
- Which products and versions are affected?
- LobeHub LobeChat through 2.2.9.
- Is there a fix for CVE-2026-58580?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-58580 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-58580?
- Check whether you run LobeHub LobeChat at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
LobeChat's MessageModel implementation contains a Broken Object-Level Authorization (BOLA) vulnerability (CWE-639). Specifically, the updateMessagePlugin, updatePluginState, updatePluginError, updateTTS, and updateTranslate methods filter database rows using only the message ID, failing to include the 'userId' scope required for multi-tenant isolation. An authenticated attacker can reach these methods via tRPC procedures and overwrite a victim's plugin tool-call metadata, state, text-to-speech, or translation records. Because the findMessagePlugin method also lacks user-scoping, the tampered content is served back to the victim. Exploitation is limited by the requirement that the attacker must obtain the victim's non-enumerable 12-character message identifier (nanoid).
Affected products
- LobeHub LobeChat through 2.2.9
Timeline
- 2026-06-04: disclosed: Private disclosure to vendor via GitHub Security Advisory
- 2026-07-02: advisory: Public disclosure and NVD publication