Skip to content
CVE-2026-124573: Authentication Bypass in Logseq Local HTTP API

CVE-2026-124573: Authentication Bypass in Logseq Local HTTP API

First seen 9 Nov 2026, 16:43 UTC • •

Article Content

Browse articles
ThreatCluster AI
ThreatCluster •November 9, 2026 at 16:44 UTC
  • •CVE-2026-124573 affects Logseq versions 2.0.1 and 2.0.2.
  • •The vulnerability allows remote attacks due to missing authentication.
  • •Public exploit code is available, but real-world exploitation is unconfirmed.

A vulnerability, CVE-2026-124573, was discovered in Logseq versions 2.0.1 and 2.0.2, affecting the validate-auth-token function in the Local HTTP API. This flaw allows for missing authentication, enabling potential remote attacks. The exploit has been made public, but real-world exploitation remains unconfirmed. The project was notified of the issue early but has not yet responded. Users of the desktop application, particularly those on shared networks, are most at risk. Immediate action is advised to check for unexpected inbound connections and review API activity. A vendor fix is awaited, and until then, disabling the local API or restricting it to loopback is recommended.

Start a free Starter trial for enhanced analysis

Ask AI about this cluster

Timeline

2026-11-09
CVE-2026-124573 published
Logseq vulnerability disclosed, affecting versions 2.0.1 and 2.0.2, with missing authentication in the Local HTTP API.
Redpacketsecurity
2026-11-09
Exploit made public
Public exploit code for CVE-2026-124573 released, raising concerns about potential remote attacks.
Sploitus

More articles in this cluster (7)

Following this threat?

Track CVE-2026-124573 in your own feed — you're alerted when they show up in new reporting, leak sites or exploitation.

Free account · no card needed

Common questions

Which Logseq versions are affected?
Logseq versions 2.0.1 and 2.0.2 are affected by CVE-2026-124573.
Is there a patch available?
A vendor fix has not yet been released; users should monitor for updates.
What immediate actions should I take?
Disable the local API if possible, or restrict it to loopback access until a patch is available.