Skip to main content
VulnerabilityPublished

CVE-2026-124573: logseq 2.0.1/2.0.2 · Improper Authentication

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-124573· Medium 6.9

Public exploit available · CVSS 6.9 Medium.

Data as of 9 Nov 2026, 10:32 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulDB)CVSS 4.06.9
CNA (VulDB)CVSS 3.17.3
CNA (VulDB)CVSS 3.07.3
CNA (VulDB)CVSS 2.07.5
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 9 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    CVSS exploit maturity: proof of concept public

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 8 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
logseqAffected
  • =2.0.1
  • =2.0.2
Fixed in–
npmlogseqpkg:npm/logseqOther threatsAffected
  • =2.0.1
  • =2.0.2
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Users should consider mitigating exposure by restricting network access to the affected Local HTTP API or disabling it if possible until a patch is released. Monitor vendor communications for updates and apply patches promptly once available.

Description

A vulnerability in Logseq versions 2.0.1 and 2.0.2 affects the validate-auth-token function in the Local HTTP API component, resulting in missing authentication. This flaw can be exploited remotely without privileges or user interaction. Public exploit code exists, but the vendor has not yet responded or issued a fix.

References

Community reviews

Loading reviews…