# CVE-2023-3891: Lapce v0.2.8 - Privilege escalation via Race Condition

> A race condition in Lapce allows attackers to elevate privileges on the system, requiring users to update the editor.

- **Severity:** High 7.3 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 15 Sep 2023
- **Updated:** 25 Sep 2025
- **Also known as:** GHSA-hww9-gvfj-fjcw

## What is CVE-2023-3891?

CVE-2023-3891 is a high-severity vulnerability in Lapce, published on 15 Sep 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Race condition in Lapce v0.2.8 allows an attacker to elevate privileges on the system

Weakness: CWE-367 (Time-of-check Time-of-use (TOCTOU) Race Condition)

## Which versions are affected by CVE-2023-3891?

It affects 1 product.


Products: Lapce Lapce.

## How do I fix CVE-2023-3891?

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

## Is CVE-2023-3891 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-3891 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-3891 and fix it if it is affected.

What it is: CVE-2023-3891 is a high-severity vulnerability in Lapce, published on 15 Sep 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-3891 exists.

Affected product: Lapce. 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-2023-3891/ (Markdown: https://insights.sbomify.com/CVE-2023-3891/index.md)
```

## Sources

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

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