# CVE-2026-47899: Arbitrary File Read, Write, Rename, and Delete in Logseq

> Attackers with renderer code execution can read, write, or delete arbitrary files via insecure IPC handlers in Logseq.

- **Severity:** High 8.7 (`CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Jun 2026
- **Updated:** 9 Jun 2026
- **Also known as:** GHSA-jq3m-h4m5-r9j5

## What is CVE-2026-47899?

CVE-2026-47899 is a high-severity path traversal vulnerability in logseq, published on 9 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The Electron preload script in Logseq exposes an API method that allows the renderer process to invoke IPC handlers without proper path validation. An attacker with JavaScript execution in the renderer (e.g. via XSS or a malicious plugin), can read, write, or delete arbitrary files on the user's system.
While only version v0.10.15 was tested and confirmed as vulnerable, status of other versions is unknown since this issue was not addressed by a patch.

Weakness: CWE-749 (Exposed Dangerous Method or Function)

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


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

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

## Is CVE-2026-47899 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-47899 is a high-severity path traversal vulnerability in logseq, published on 9 Jun 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-47899 in the wild and no public exploit code.

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

## Sources

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

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