dbcve.org
Code InjectionWeakness · CWE-94

CVE-2026-23733

MEDIUM · 6.4 CVSS v3.1 Published 2026-01-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
64/100
Remediation priority · Elevated

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A stored Cross-Site Scripting (XSS) vulnerability exists in LobeChat's Mermaid artifact renderer (versions prior to 2.0.0-next.180). Attackers inject malicious JavaScript through Mermaid diagrams that persists and executes in victims' browsers. This XSS escalates to Remote Code Execution via the exposed `electronAPI` IPC bridge, enabling arbitrary system command execution on victim machines.

MitigationUpgrade to LobeChat version 2.0.0-next.180 or later to patch the vulnerability. As a temporary workaround, restrict or disable the Mermaid artifact renderer until the upgrade can be applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
High
Privileges
High
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
Low
Availability
Low

CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:C/C:H/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify LobeChat installation and type
    Determine if LobeChat is running as a web application (hosted) or as an Electron desktop application. For web, check the URL and hosting environment. For desktop, check for the LobeChat application binary or running process.
    Affected if LobeChat is installed and accessible (either web or Electron desktop)
  2. Determine installed LobeChat version
    For web deployments, check the version displayed in the UI footer or examine the JavaScript bundle/source code for version strings. For Electron desktop, check the application's About section or examine package.json within the application files.
    Affected if The version is lower than 2.0.0-next.180 (e.g., 2.0.0-next.179, 1.x series, etc.)
  3. Verify Mermaid artifact renderer is enabled
    Check if the Mermaid diagram rendering feature is accessible within LobeChat. This may appear as a code block renderer, artifact preview, or diagram viewer feature in the chat interface.
    Affected if The Mermaid renderer feature is available and enabled in the environment
  4. Confirm Electron desktop context for RCE vector
    If running as an Electron desktop application, verify the presence of the electronAPI interface. This IPC bridge is typically exposed to renderer processes in Electron apps. Check browser developer console (if accessible) or examine application code for electronAPI references.
    Affected if LobeChat runs as an Electron desktop application with electronAPI exposed to the renderer process

A user is affected if LobeChat version is prior to 2.0.0-next.180, the Mermaid artifact renderer is enabled, and (for RCE escalation) the application runs as an Electron desktop client exposing the electronAPI IPC bridge.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to LobeChat version 2.0.0-next.180 or later to patch the vulnerability. As a temporary workaround, restrict or disable the Mermaid artifact renderer until the upgrade can be applied.

Recommended fix High confidence

2.0.0-next.180

  1. 1. Backup your current LobeChat installation and any important data
  2. 2. Identify your current LobeChat version by checking the application or package.json
  3. 3. Update to version 2.0.0-next.180 or later using your package manager (e.g., npm install @lobehub/[email protected] or equivalent)
  4. 4. If using Docker, pull the updated container image with the fixed version tag
  5. 5. After upgrading, verify the application starts correctly
  6. 6. Test that the Mermaid artifact renderer functions properly with the update
  7. 7. If this is an Electron-based deployment, ensure the electronAPI bridge exposure is reviewed per the patch notes
Caveat This is a prerelease version (next branch); may include other unstable features or breaking changes beyond the security fix

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,540
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,464.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-23733 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-23733 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data