CVE-2026-124573
logseq Local HTTP API server.cljs validate-auth-token missing authentication
A vulnerability was found in logseq 2.0.1/2.0.2. This affects the function validate-auth-token of the file src/electron/electron/server.cljs of the component Local HTTP API. The manipulation results in missing authentication. The attack may be performed from remote. The exploit has been made public and could be used. The project was informed of the problem early through an issue report but has not responded yet.
Fixes and workarounds
No remediation reported in collected sources.
Missing remediation information is not evidence that no patch exists.
Affected products and versions
| Product | Versions | Authority |
|---|---|---|
| logseq n/a |
2.0.1 (affected) 2.0.2 (affected) |
CNA: VulDB |
Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.
CVSS assessments
| Version / score | Vector | Authority |
|---|---|---|
| 4.0 / 6.9 medium |
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 | CNA: VulDB |
| 3.1 / 7.3 high |
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L/E:P/RL:X/RC:C | CNA: VulDB |
| 3.0 / 7.3 high |
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L/E:P/RL:X/RC:C | CNA: VulDB |
| 2.0 / 7.5 high |
AV:N/AC:L/Au:N/C:P/I:P/A:P/E:POC/RL:ND/RC:C | CNA: VulDB |
Exploit evidence
- https://github.com/logseq/logseq/issues/13596
exploit · CNA: VulDB
References
- https://vuldb.com/vuln/432919CNA: VulDB · vdb-entry, technical-description
- https://vuldb.com/vuln/432919/ctiCNA: VulDB · signature, permissions-required
- https://vuldb.com/cve/CVE-2026-124573CNA: VulDB · third-party-advisory
- https://vuldb.com/submit/1035945CNA: VulDB · third-party-advisory
- https://github.com/logseq/logseq/issues/13596CNA: VulDB · exploit, issue-tracking
- https://github.com/logseq/logseq/CNA: VulDB · product
For agents and automation
Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.
Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.
Endpoints and access details
https://api.y2.dev/api/v2/cyber/cveshttps://api.y2.dev/api/v2/cyber/cves/{cveId}
A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.
For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.