Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-23733: CWE-94: Improper Control of Generation of Code ('Code Injection') in lobehub lobe-chat

0
Medium
VulnerabilityCVE-2026-23733cvecve-2026-23733cwe-94
Published: Sun Jan 18 2026 (01/18/2026, 22:56:15 UTC)
Source: CVE Database V5
Vendor/Project: lobehub
Product: lobe-chat

Description

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.

AI-Powered Analysis

AILast updated: 01/26/2026, 19:56:57 UTC

Technical Analysis

CVE-2026-23733 is a vulnerability classified under CWE-94 (Improper Control of Generation of Code), affecting the LobeChat open source chat application platform. The flaw exists in versions prior to 2.0.0-next.180 and stems from a stored Cross-Site Scripting (XSS) vulnerability within the Mermaid artifact renderer component. This renderer improperly sanitizes user-supplied input, allowing attackers to inject and store malicious JavaScript code. When a victim views the affected artifact, the malicious script executes within the application's context. Critically, LobeChat exposes an electronAPI IPC bridge that facilitates inter-process communication between the renderer and the underlying operating system. Attackers can leverage this bridge to escalate the XSS into Remote Code Execution (RCE), enabling arbitrary system command execution on the victim's machine. The CVSS 3.1 base score is 6.4 (medium), reflecting that exploitation requires local access (AV:L), high attack complexity (AC:H), privileges (PR:H), and user interaction (UI:R). The vulnerability impacts confidentiality (high), integrity (low), and availability (low) due to the potential for system command execution. No public exploits are known, but the risk is significant for environments where users run vulnerable LobeChat versions with elevated privileges. The issue is resolved in version 2.0.0-next.180, which includes proper input sanitization and hardened IPC controls.

Potential Impact

For European organizations, this vulnerability poses a risk primarily to environments where LobeChat is deployed and used by privileged users. Successful exploitation could lead to unauthorized system command execution, potentially compromising sensitive data, disrupting services, or enabling lateral movement within networks. Confidentiality is most at risk due to arbitrary code execution capabilities. The requirement for local access and user interaction limits widespread remote exploitation but does not eliminate insider threat or targeted attack scenarios. Organizations relying on LobeChat for internal communications, especially in sectors like technology, finance, or government, could face operational disruptions or data breaches if the vulnerability is exploited. The medium severity rating suggests moderate urgency, but the ability to escalate from XSS to RCE elevates the potential impact. Given the open source nature of LobeChat, organizations using customized or self-hosted deployments should be particularly vigilant.

Mitigation Recommendations

European organizations should immediately verify their LobeChat versions and upgrade to 2.0.0-next.180 or later to apply the official patch. Beyond patching, organizations should implement strict privilege management to limit the number of users with high-level access to LobeChat instances. Employ application whitelisting and endpoint detection and response (EDR) solutions to monitor and block suspicious system command executions originating from LobeChat processes. Network segmentation can reduce the impact of a compromised host. Disable or restrict the electronAPI IPC bridge if possible, or apply additional sandboxing to limit its capabilities. Conduct user training to raise awareness about the risks of interacting with untrusted content within chat applications. Regularly audit and sanitize user-generated content to prevent injection of malicious scripts. Finally, monitor logs for unusual activity related to LobeChat usage and IPC communications.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-01-15T15:45:01.957Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 696d68b1d302b072d904d564

Added to database: 1/18/2026, 11:11:45 PM

Last enriched: 1/26/2026, 7:56:57 PM

Last updated: 2/7/2026, 1:45:05 AM

Views: 32

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats