External risk intelligence

SiYuan Kernel Unthrottled API Token Brute Force

CVE advisorySeverity: CRITICAL (CVSS 9.3)

CVE-2026-73056

SiYuan is a personal knowledge management tool primarily intended for local or private use. While it includes an API that may be exposed to the network, public internet exposure is not the default or intended deployment pattern for this type of application, making remote reachability possible but not common for typical users.

Halo Surface Signal: 3 out of 5 — possibly public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A vulnerability in SiYuan kernel's authentication mechanism allows unauthenticated remote attackers to guess API tokens, potentially gaining full administrative access and enabling arbitrary file operations and SQL queries. This could impact systems where the API token is short or weak and exposed.

Attackers can guess API tokens without limits.
This could grant unauthorized administrator access.
Confirm relevance and exposure of API tokens.

Attack Path

How an attacker could exploit the issue

An attacker can bypass security measures by sending API tokens directly in the URL or a request header, without being subjected to any attempt-limiting controls. This allows them to repeatedly guess the API token until they succeed, gaining administrative privileges.

Unauthenticated remote access required.
API token bypass triggers vulnerability.
Full administrative access granted.

Live Threat

Current exploitation, exposure, and threat context

An unauthenticated remote attacker could gain full administrative access by repeatedly guessing the API token through the Authorization header or a query parameter. This is possible when the application's rate limiting or CAPTCHA mechanisms do not protect these authentication methods. Successful exploitation could allow an attacker to perform arbitrary file operations and execute SQL queries.

Administrative access and system files.
Unlimited automated API token guesses.
Arbitrary file operations and SQL queries.

Operational Fix

Recommended remediation, mitigation, and detection steps

Application and platform teams are likely responsible for addressing this critical vulnerability in the SiYuan kernel's authentication middleware. The immediate priority is to identify all instances of the affected technology, determine their network exposure and business criticality, and then locate the accountable owner for each instance. Remediation planning should follow, prioritizing the most exposed and critical systems.

Identify accountable application/platform owners.
Verify network exposure and business criticality.
Plan remediation based on risk and impact.

Supplementary metadata

CVSS vector

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Free EASM Trial See How Signal Works

Frequently asked questions

What is SiYuan and how is it typically used?

SiYuan is a personal knowledge management tool designed to help users organize information. It functions as a local server, often running on a user's machine or within a private network to store notes and data. Because it includes an API for automation and integration, it can sometimes be configured to accept network connections beyond the local host.

What does CWE-307 mean for CVE-2026-73056?

CWE-307, or Improper Restriction of Excessive Authentication Attempts, identifies a flaw where a system lacks safeguards against repeated login tries. In this CVE, the SiYuan kernel fails to apply its lockout or CAPTCHA protections to the API token verification process. This weakness allows an attacker to automate thousands of guesses to find a valid token without ever being blocked by the software.

How can an attacker trigger this authentication bypass?

The vulnerability is triggered by sending API token guesses through the Authorization header or a URL query parameter. Crucially, the system does not monitor these specific paths for rapid-fire attempts. If a user utilizes a long, complex, randomly generated token, it remains difficult to crack; the attack primarily succeeds against short or weak tokens that are easily guessed via automation.

Is my SiYuan instance at risk from the internet?

Halo Surface Signal indicates that while SiYuan is typically deployed for private use, any instance reachable via the public internet increases the likelihood of unauthorized access. If your installation is confined to a local or internal network without public routing, the barrier to an attacker is significantly higher. You should verify if your specific configuration inadvertently exposes the API port to external networks.

How do I secure my SiYuan installation?

Start by identifying all deployed instances of the SiYuan kernel to assess their current network exposure and business importance. If an instance is exposed, confirm the strength of your configured API token, as weak tokens are the primary point of failure. Coordinate with your team to prioritize updates to version 3.7.4 or later, which addresses the lack of authentication rate limiting in the middleware.

References

Written by Nicholas Merritt

Nicholas Merritt is VP of Security Solutions at Halo Security. With more than 25 years across application security, vulnerability prioritization, and offensive security, he helps teams translate threat data into practical exposure validation and remediation focus. He authors Halo Threat Intelligence CVE advisories using Halo Surface Signal and H/A/L/O context to prioritize internet-facing risk.