LobeHub has a Cross-Site Scripting issue that escalates to Remote Code Execution

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

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

EPSS

• CVE-2026-42045: 0.27% estimated exploitation activity in the next 30 days; percentile 18.54 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary The vulnerability was automatically discovered by an ai agent and then manually verified. LobeChat's message rendering mechanism has a stored cross-site scripting (XSS) vulnerability. Combined with the Electron main process's exposed insecure IPC interface, attackers can construct malicious payloads to achieve an attack chain from XSS to remote code execution (RCE). The LobeChat team verified this vulnerability in lobehub v2.1.23, and it also exists in the latest version. Details When LobeChat processes custom tags in the Render process of src/features/Portal/Artifacts/Body/Renderer/index.tsx, if no type match is found, it will choose to call the default method, HTMLRenderer, for HTML rendering. If an attacker can induce the LLM to output content containing malicious tags, an XSS vulnerability can be created on the client side. Additionally, Lobechat's Electron main process exposes an IPC interface called runCommand, used to invoke system commands. This interface allows…

Published by the source

5 May 2026, 18:04 UTC

Last modified by the source

13 May 2026, 16:33 UTC

Source last checked

26 Oct 2026, 12:52 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-xq4x-622m-q8fq

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-xq4x-622m-q8fq

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-42045

Advisory: LobeHub has a Cross-Site Scripting issue that escalates to Remote Code Execution
IDs: CVE-2026-42045, GHSA-xq4x-622m-q8fq
Record: https://patchnext.com/advisories/cve-2026-42045 (revision 2, source checked 26 Oct 2026, 12:52 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.2)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @lobehub/lobehub: affected <= 2.1.26

## Suggested inspection (read-only)
- `npm ls @lobehub/lobehub --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @lobehub/lobehub.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-xq4x-622m-q8fq (OSV record GHSA-xq4x-622m-q8fq lists affected ranges: npm @lobehub/lobehub >=0 <=2.1.26)
- Verified: https://github.com/advisories/GHSA-xq4x-622m-q8fq (GitHub-reviewed advisory GHSA-xq4x-622m-q8fq lists affected ranges: npm @lobehub/lobehub >=0 <=2.1.26)

Commands are suggestions: review each one before running it.