CVE-2026-23733
Lobe Chat has Cross-Site Scripting (XSS) issue that may escalate to Remote Code Execution (RCE)
No known exploitation. EPSS puts it in the 4th percentile. No fix published yet.
No public exploit knownFixNone yetNo fix or workaround published
No ready-made check. Neither Nuclei nor OpenVAS has one for this CVE yet.
What to do
No fixed build or workaround is published yet. Limit exposure and watch for a patch.
- Lobehub Lobe-chatAffected: < 2.0.0-next.180Upgrade to: not statedStated by: CVE record
- Npm @lobehub/chatAffected: ≤ 1.143.2Upgrade to: after 1.143.2Stated by: GitHub advisory
Versions as the sources state them. Full version matrix after sign-in
What it is
From the CVE record
LobeChat is an open source chat application platform. Prior to version 2.0.0-next.180, a stored Cross-Site Scripting (XSS) vulnerability in the Mermaid artifact renderer allows attackers to execute arbitrary JavaScript within the application context. This XSS can be escalated to Remote Code Execution (RCE) by leveraging the exposed `electronAPI` IPC bridge, allowing attackers to run arbitrary system commands on the victim's machine. Version 2.0.0-next.180 patches the issue.
In plain language
No plain-language summary for this CVE yet.
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- CISA KEV
Not in the catalog. CISA has not confirmed exploitation.
- Public exploits
No public exploit or proof of concept found in the sources we track.
- EPSS
0.1% chance of exploitation activity in the next 30 days, which ranks it in the 4th percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
Lifecycle
4 events over 8 days, from the signal feeds we watch.
- Record updated
- Publishedweakness classified, att&ck mapped
Affected products
Technical detail
CVSS 3.1 vector
Open in the CVSS calculatorCVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:C/C:H/I:L/A:L
Scored 6.4 by NVD.
How it is reached
- Attack Vector LocalRequires local access to the vulnerable system (e.g. local login, malicious file)
- Attack Complexity HighRequires specific conditions like a race condition or non-default configuration
- Privileges Required HighRequires admin or elevated privileges
- User Interaction RequiredA user must click a link, open a file, or perform some action
Scope
- Scope ChangedThe exploit can affect other components (e.g. sandbox escape, host compromise from VM)
Impact if exploited
- Confidentiality HighTotal information disclosure — all data in the component is compromised
- Integrity LowData modification is possible but limited in scope or consequence
- Availability LowReduced performance or intermittent disruption of service
Weaknesses
ATT&CK techniques
Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.
Sources
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for Lobe-chat, not every advisory.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI