External risk intelligence

Logseq Marketplace XSS Vulnerability Allows Code Execution

CVE advisorySeverity: CRITICAL (CVSS 9.6)

CVE-2025-56683

Logseq is a local-first, privacy-focused note-taking application intended for personal use on individual devices. It does not operate as a public-facing web server, API, or internet gateway. The vulnerability requires a user to interact with a crafted file locally, making public network exposure of this attack surface extremely unlikely in typical deployments.

Cross-site Scripting

Halo Surface Signal: 1 out of 5 — much less likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This advisory addresses a critical vulnerability affecting Logseq, a note-taking application. The flaw allows for arbitrary code execution if a user interacts with a specially crafted file. While Logseq is designed for local, personal use and not typically exposed to the internet, the severity of the vulnerability necessitates confirming its relevance and any potential exposure within your environment.

  • Unsafe file handling allows code execution.
  • Critical flaw in a widely used note-taking tool.
  • Confirm relevance and exposure within your systems.

Attack Path

How an attacker could exploit the issue

An attacker could trick a user into opening a specially crafted README.md file, which would then inject malicious JavaScript into the application. This could allow the attacker to execute arbitrary code within the context of the user's session.

  • Requires user interaction with a crafted file.
  • Injects arbitrary JavaScript into README.md.
  • Enables arbitrary code execution.

Live Threat

Current exploitation, exposure, and threat context

A cross-site scripting vulnerability exists that could allow an attacker to execute arbitrary JavaScript code when a user opens a specially crafted README.md file within the application. This could affect the application's behavior and potentially expose user data handled by the application.

  • Application functionality and user data.
  • User opens a malicious README.md file.
  • Arbitrary code execution and data exposure.

Operational Fix

Recommended remediation, mitigation, and detection steps

Identifying the scope and impact of this vulnerability requires coordination between application owners, who manage the Logseq instances, and potentially infrastructure or security teams if Logseq is deployed in a shared environment. The first practical step is to determine where Logseq is deployed, ascertain if any instances are exposed externally or handle sensitive data, and identify the accountable user or team for each instance to plan remediation.

  • Application owners should manage remediation.
  • Verify user interaction with crafted files.
  • Plan updates or de-provisioning.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is Logseq?

Logseq is a privacy-focused, open-source note-taking application designed for personal knowledge management. It stores files locally on a user's device rather than on a central server, allowing people to organize thoughts, tasks, and journals in a flexible, local-first environment.

What does CWE-79 mean for CVE-2025-56683?

CWE-79 refers to Cross-Site Scripting (XSS). In the context of this vulnerability, it means the application fails to properly sanitize input in its marketplace component. This allows malicious JavaScript to be hidden within a README.md file, which the software then incorrectly executes when that file is viewed.

How is this vulnerability triggered?

An attacker must successfully induce a user to open a specifically crafted README.md file within the affected Logseq component. Simply having the file on your computer does not trigger the bug; the vulnerability remains dormant until the user interacts with the file through the application.

Is my Logseq installation at risk?

Halo Surface Signal indicates that public network exposure is very unlikely because Logseq is a local-first, personal tool rather than a public-facing web server. The primary risk exists if you frequently open untrusted files from external sources within the application.

What should I do if I use Logseq?

Your first step is to identify where you have Logseq installed and determine who manages those instances. Evaluate whether you handle sensitive data and exercise caution by only opening README.md files from trusted sources until you can verify your software version and plan for necessary updates.

References