# CVE-2026-47899: Logseq exposed dangerous IPC method in Electron preload script

Source: https://junglewise.ai/threats/cve-2026-47899-logseq-exposed-dangerous-ipc-method-in-electron-preload-script  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-06-09. Updated: 2026-06-09  
License: CC BY 4.0 with a link back

CVE-2026-47899 · Severity: info · CVSS 8.7 · Published 2026-06-09

Logseq, a popular open-source knowledge management and note-taking application, contains a security flaw in how it handles internal communications. If an attacker manages to run malicious code within the app—for example, through a compromised plugin or a separate web-based attack—they could bypass security restrictions to read, modify, or delete any file on your computer. This could lead to the theft of sensitive personal notes or the destruction of important data.

Technologies: [Logseq](https://junglewise.ai/threats/technologies/logseq). Vendors: [Logseq](https://junglewise.ai/threats/vendors/logseq).

## Quick answers

**Is CVE-2026-47899 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-47899 being exploited in the wild.

**How severe is CVE-2026-47899?** Informational severity, with a CVSS score of 8.7, published 9 June 2026.

**Which products and versions are affected?** Logseq All through 0.10.15.

**Is there a fix for CVE-2026-47899?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2026-47899 attacked?** It is attacked with local access, in a network appliance.

**Am I affected by CVE-2026-47899?** Check whether you run Logseq 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.

## Technical details

The vulnerability exists within Logseq's Electron preload script, which improperly exposes an API method to the renderer process. This method allows the invocation of Inter-Process Communication (IPC) handlers without sufficient path validation. An attacker who achieves JavaScript execution within the renderer process—potentially via a Cross-Site Scripting (XSS) vulnerability or a malicious third-party plugin—can leverage this exposed method to perform unauthorized file operations. Specifically, the attacker can read, write, or delete arbitrary files with the privileges of the Logseq application. As of the advisory date, no patch has been released by the vendor.

## Affected products

- Logseq Logseq All through 0.10.15

## Timeline

- 2026-06-09: disclosed: Vulnerability disclosed by CERT Polska
- 2026-06-09: advisory

## References

- [https://cert.pl/en/posts/2026/06/CVE-2026-9279/](https://cert.pl/en/posts/2026/06/CVE-2026-9279/)
- [https://logseq.com/](https://logseq.com/)

## Related threats

- [Logseq missing authentication in Local HTTP API](https://junglewise.ai/threats/cve-2026-124573-a-vulnerability-was-found-in-logseq-2-0-1-2-0-2-this-affects-the)
- [Logseq OS command injection in IPC handler](https://junglewise.ai/threats/cve-2026-9279-logseq-os-command-injection-in-ipc-handler)
- [Logseq sandbox escape via plugin HTML attribute injection](https://junglewise.ai/threats/cve-2026-47901-logseq-sandbox-escape-via-plugin-html-attribute-injection)
- [Logseq stored XSS in plugin package.json name field](https://junglewise.ai/threats/cve-2026-47900-logseq-stored-xss-in-plugin-package-json-name-field)