Quick answers
- Is CVE-2026-120315 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-120315 being exploited in the wild.
- How severe is CVE-2026-120315?
- High severity, with a CVSS score of 8.8, published 2 November 2026.
- Which products and versions are affected?
- LobeHub Chat 1.84.26 before 2.1.49.
- Is there a fix for CVE-2026-120315?
- Yes: fixed in 2.1.49. Until then: Restrict access to the file.createFile and document.parseFile tRPC endpoints to trusted users only, or disable document parsing functionality until an upgrade is available. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-120315 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-120315?
- Check whether you run LobeHub Chat at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 2.1.49
Restrict access to the file.createFile and document.parseFile tRPC endpoints to trusted users only, or disable document parsing functionality until an upgrade is available.
Technical details
The vulnerability exists in src/server/utils/tempFileManager.ts where unsanitized user-supplied filenames from the database are passed directly to path.join() during document parsing. An authenticated attacker can craft a file record via file.createFile with a path traversal payload (e.g., ../../../app/startServer.js), then trigger DocumentService.parseFile() to write attacker-controlled content to arbitrary locations. This enables code execution via overwriting application files or denial of service through file corruption.
Affected products
- LobeHub Chat 1.84.26 before 2.1.49
Timeline
- 2026-10-17: disclosed: GitHub Security Advisory GHSA-2g9j-v25c-4j97 published
- 2026-11-02: advisory: CVE-2026-120315 assigned