# CVE-2026-47901: Logseq sandbox escape via plugin HTML attribute injection

Source: https://junglewise.ai/threats/cve-2026-47901-logseq-sandbox-escape-via-plugin-html-attribute-injection  
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-47901 · Severity: info · CVSS 4.6 · Published 2026-06-09

Logseq, a popular open-source knowledge management and note-taking application, contains a security flaw in how it handles third-party plugins. A malicious plugin could bypass security restrictions to run unauthorized code on a user's computer. This could allow an attacker to access, modify, or delete private files and data stored on the local system.

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

## Quick answers

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

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

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

**Is there a fix for CVE-2026-47901?** 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-47901 attacked?** It is attacked with local access, in a network appliance.

**Am I affected by CVE-2026-47901?** 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

Logseq is vulnerable to a sandbox escape (CWE-79) within its plugin architecture. Plugins running in sandboxed iframes can inject arbitrary HTML attributes, such as event handlers, into their container element in the host DOM. Because the Content Security Policy (CSP) is disabled, this allows a malicious plugin to execute arbitrary JavaScript within the privileged host context. An attacker can leverage this to gain unauthorized access to sensitive filesystem APIs. The vulnerability was confirmed in version 0.10.15 and is reported to affect all versions through that release, as no patch has been issued 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 stored XSS in plugin package.json name field](https://junglewise.ai/threats/cve-2026-47900-logseq-stored-xss-in-plugin-package-json-name-field)
- [Logseq exposed dangerous IPC method in Electron preload script](https://junglewise.ai/threats/cve-2026-47899-logseq-exposed-dangerous-ipc-method-in-electron-preload-script)