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

6.9MEDIUM

Key Information:

Vendor

Logseq

Status
Logseq
Vendor
CVE Published:
9 November 2026

Badges

👾 Exploit Exists🟡 Public PoC

What is CVE-2026-124573?

A significant vulnerability exists in Logseq versions 2.0.1 and 2.0.2, specifically within the Local HTTP API's token validation function. This flaw enables unauthorized access due to missing authentication checks, potentially allowing attackers to exploit the application remotely. Despite notification of the issue, there has been no response from the developers, leaving systems vulnerable. The issue poses serious risks, emphasizing the need for immediate awareness and action from users.

Affected Version(s)

logseq 2.0.1

logseq 2.0.2

Exploit Proof of Concept (PoC)

PoC code is written by security researchers to demonstrate the vulnerability can be exploited. PoC code is also a key component for weaponization which could lead to ransomware.

CVE-2026-124573 - Proof of Concept

References

https://vuldb.com/vuln/432919
vdb-entrytechnical-description
https://vuldb.com/vuln/432919/cti
signaturepermissions-required
https://vuldb.com/cve/CVE-2026-124573
third-party-advisory

CVSS V4

Score:
6.9
Severity:
MEDIUM
Confidentiality:
Low
Integrity:
Low
Availability:
Low
Attack Vector:
Network
Attack Complexity:
Low
Attack Required:
None
Privileges Required:
Undefined
User Interaction:
None

Timeline

  • 🟡

    Public PoC available

  • 👾

    Exploit known to exist

  • Vulnerability published

  • Vulnerability Reserved

Credit

akamoli (VulDB User)
VulDB CNA Team
.