Skip to content
CVE Alert: CVE-2026-124573 – n/a

CVE Alert: CVE-2026-124573 – n/a

Redpacketsecurity •admin • November 9, 2026

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.

**Risk verdict:** Treat this as an urgent exposure check: public exploit code is indicated, but KEV, SSVC and EPSS status were not provided.

**Why this matters:** A reachable unauthenticated API could let an attacker access or alter information handled by the application, or disrupt its operation. For a knowledge-management tool, that may expose sensitive notes or undermine their integrity; public exploit availability raises concern, though real-world exploitation is unconfirmed.

**Most likely attack path:** The attack appears to require network reachability, but no account, special timing or user action. The affected process is likely the boundary of impact; onward movement is not established, although exposed data or a compromised user workflow could provide a stepping stone. Whether remote access is practical depends on how the local API binds and on host and network controls.

**Who is most exposed:** Users running the desktop application on systems where its local API is reachable beyond the host are the main concern, particularly on shared networks or managed workstations. Confirm actual listener exposure rather than assuming it is limited to loopback.

Check for unexpected inbound connections to the application’s API port.

Review endpoint and firewall logs for requests from non-local addresses.

Look for unusual API activity or unexpected changes to local knowledge files.

Mitigation and prioritisation:

Identify affected installations and apply a vendor fix when available; confirm remediation status before broad rollout.

Until then, disable the local API if feasible or restrict it to loopback with host firewall rules.

Validate binding and access controls after updates; test representative workflows before deployment.

No KEV or EPSS threshold is established from the supplied data; reassess urgency if those signals become available.

A considerable amount of time and effort goes into maintaining this website, creating backend automation and creating new features and content for you to make actionable intelligence decisions. Everyone that supports the site helps enable new functionality.

If you like the site, please support us on Patreon or Buy Me A Coffee using the buttons below.

Extracted Entities