# CVE-2026-19054: Lspace-io lspace-server Repositories File API repository.ts deleteFile path traversal

> Local attackers can exploit path traversal in the Repositories File API to read or modify arbitrary files via manipulated file paths.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Aug 2026
- **Updated:** 7 Aug 2026
- **Also known as:** GHSA-539j-9cqc-ppx4

## What is CVE-2026-19054?

CVE-2026-19054 is a medium-severity path traversal vulnerability in Lspace-io lspace-server, published on 6 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability was detected in Lspace-io lspace-server up to 79f02fe5aa8970b210a6a05cf097155f8d9ffd71. This issue affects the function fileExists/readFile/writeFile/deleteFile of the file src/core/repository.ts of the component Repositories File API. Performing a manipulation of the argument filePath results in path traversal. The attack is only possible with local access. Continious delivery with rolling releases is used by this product. Therefore, no version details of affected nor updated releases are available. The project was informed of the problem early through an issue report but has not responded yet.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-19054?


## How do I fix CVE-2026-19054?

No fix has been published for CVE-2026-19054 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-19054 being exploited?

There is no known exploitation of CVE-2026-19054 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-19054 and fix it if it is affected.

What it is: CVE-2026-19054 is a medium-severity path traversal vulnerability in Lspace-io lspace-server, published on 6 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-19054 in the wild and no public exploit code.

Affected product: Lspace-io lspace-server. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-19054/ (Markdown: https://insights.sbomify.com/CVE-2026-19054/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-19054
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-19054
- OSV: https://osv.dev/vulnerability/CVE-2026-19054

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-19054/
Summaries are generated and may contain mistakes; the official description above is the record.