/

CVE-2026-73045

Severity:

HIGH RISK

(7.5)

Brute-Force (CWE-307) in SiYuan authFilePublish

CVE-2026-73045

Deferred

Vulnerability type

Category:

Insufficient Protection Against Authentication Attempts

CWE:

CWE-307

Impact:

Unauthorized Access to Published Notebooks

Severity:

HIGH RISK

(7.5)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

SiYuan's authFilePublishAccess endpoint does not adequately restrict repeated authentication attempts for password-protected published notebooks. An unauthenticated attacker may submit unlimited password guesses and gain access when the notebook's publish password is weak or guessable.

Affected context

The vulnerability occurs in SiYuan deployments that expose the authFilePublishAccess endpoint for password-protected notebook publishing. Risk increases when the endpoint permits repeated unauthenticated guesses without effective rate limiting, CAPTCHA, lockout, or equivalent abuse controls.

Exploit preconditions

  • Attack surface: The SiYuan authFilePublishAccess endpoint
  • Required access: No authentication is required to submit password attempts
  • Trigger point: Repeated authentication requests for a published notebook
  • Why exploitation is possible: The endpoint accepts unbounded guesses without sufficient throttling or challenge mechanisms

Why this happens

The underlying bug is insufficient enforcement of authentication-attempt limits. A password verification endpoint accepts repeated requests without applying effective rate limits, progressive delays, CAPTCHA challenges, or equivalent controls. This behavior maps to CWE-307: Improper Restriction of Excessive Authentication Attempts, because the system does not adequately constrain automated password guessing.

Potential impact

  • An attacker may gain unauthorized access to password-protected published notebooks
  • Private notebook content could be disclosed
  • Exposed information could support further attacks against users or infrastructure
  • Repeated guessing activity could consume endpoint or application resources

General mitigation guidance

Mitigation generally focuses on enforcing authentication-abuse controls at the endpoint and reducing reliance on guessable shared passwords. Defensive patterns may include per-account, per-notebook, and per-source rate limits; progressive delays or temporary lockouts; CAPTCHA or equivalent challenges after suspicious activity; strong, unique password requirements; monitoring and alerting for repeated failures; and least-privilege access to published content. Controls should be applied consistently across direct and proxied access paths and should fail closed when abuse-detection services are unavailable.

How teams detect issues like this

Detection can include static and dynamic checks for authentication endpoints that lack throttling, lockout, challenge, or failure-tracking logic. Code review should examine whether limits are scoped only to easily bypassed client-controlled identifiers and whether published-resource authentication receives the same protections as other login flows. Operational monitoring can alert on bursts of failed publish-password attempts, distributed guessing patterns, and successful access following repeated failures. Automated security review tools and API testing policies may help identify missing brute-force controls.

Sources

SourceLink
github.comgithub.com/siyuan-note/siyuan/security/advisories/GHSA-v362-968x-gp2v
vulncheck.comvulncheck.com/advisories/siyuan-before-brute-force-via-authfilepublishaccess

Frequently asked

questions

Yes. It can generally be reached remotely through the published-notebook authentication endpoint, provided the endpoint is exposed to the attacker.

No authenticated account is typically required. The attacker needs the target notebook's published access path and the ability to send password attempts.

Apply server-side, resource-aware attempt limits with progressive delays or temporary blocking, and use additional challenges when guessing behavior is detected.

Threat-model every password verification endpoint, enforce centralized rate-limiting policies, require strong unique secrets, and monitor failed authentication activity for automated guessing.

Find out what's already
exploitable in your codebase.