Security readout for executives and security teams
Plain-English summary
Lobe Chat versions before 2.0.0-next.180 contain a stored XSS flaw in the Mermaid artifact renderer. In the desktop/Electron context described by the advisory, that JavaScript may reach an exposed IPC bridge and escalate to running system commands on a victim machine.
Executive priority
Prioritize patching where Lobe Chat is used on employee workstations or handles untrusted shared content. The rating is medium, but the business concern is potential endpoint command execution if the required conditions are met.
Technical view
The issue is stored XSS in Mermaid rendering, with possible RCE through the exposed electronAPI IPC bridge. The CVSS 3.1 score is 6.4: local attack vector, high complexity, high privileges required, and user interaction required, with high confidentiality impact.
Likely exposure
Organizations running lobehub/lobe-chat below 2.0.0-next.180 are potentially affected. Risk is most relevant where users open or render attacker-controlled Mermaid artifacts in an Electron-based Lobe Chat environment.
Exploitation context
No public source in the provided bundle states active exploitation, and the CVE is not listed as KEV. Exploitation appears constrained by local access, high privileges, and user interaction, but successful exploitation could lead to command execution on the victim system.
Researcher notes
Evidence is limited to the CVE record and GitHub advisory. The advisory names the vulnerable component, affected version range, patched version, and escalation path. Do not assume broader products, cloud exposure, exploit availability, or alternate fixes beyond the cited sources.
Mitigation direction
- Upgrade Lobe Chat to version 2.0.0-next.180 or later.
- Review the GitHub security advisory for any vendor-specific deployment guidance.
- Limit exposure to untrusted Mermaid artifacts until affected instances are updated.
Validation and detection
- Inventory Lobe Chat deployments and identify versions below 2.0.0-next.180.
- Confirm whether deployments use the affected Mermaid artifact renderer.
- Assess whether desktop/Electron usage exposes the electronAPI IPC bridge described in the advisory.
- Check security logs for suspicious rendered artifacts or unexpected local process activity.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-23733 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.4 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:C/C:H/I:L/A:L
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:C/C:H/I:L/A:L0.65.3Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
6.4MediumVector: CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:C/C:H/I:L/A:L
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/lobehub/lobe-chat/security/advisories/GHSA-4gpc-rhpj-9443CVE reference · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.