/

CVE-2026-74868

Severity:

HIGH RISK

(7.5)

Unthrottled Brute Force (CWE-307) in SiYuan Publish

CVE-2026-74868

Deferred

Vulnerability type

Category:

Brute-Force Authentication

CWE:

CWE-307

Impact:

Unauthorized Access to Published Content

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 Publish Service Basic Auth implementation permits unlimited password attempts against named publish-viewer accounts without throttling, lockout, or backoff. An unauthenticated remote attacker who can reach the Publish Service listener may guess credentials and access published notes or notebooks.

Affected context

The issue occurs in SiYuan deployments where the Publish Service is enabled and named accounts are protected with Basic Auth. Risk is higher when the service listener is reachable by untrusted networks, including the default TCP port 6808, and when account passwords are weak or reused.

Exploit preconditions

  • Attack surface: Network-accessible Publish Service listener
  • Required access: No prior authentication is required; the attacker must be able to connect to the listener
  • Trigger point: Repeated Basic Auth requests targeting a named publish-viewer account
  • Why exploitation is possible: The authentication flow does not enforce request throttling, account lockout, or progressive backoff, allowing unlimited password guesses

Why this happens

The vulnerability results from an authentication implementation that validates Basic Auth credentials without limiting repeated failures. This maps to CWE-307: Improper Restriction of Excessive Authentication Attempts, because the service lacks controls that constrain automated guessing against individual accounts or across the authentication endpoint.

Potential impact

  • An attacker may gain access to published notes and notebooks
  • Confidential published content could be disclosed
  • Compromised accounts may be used to access additional exposed publishing functionality
  • Repeated authentication traffic could consume service resources

General mitigation guidance

Mitigation generally focuses on enforcing controls that reduce automated credential guessing and limiting exposure of the authentication endpoint.

Common defensive patterns include:

  • Apply per-account and per-source rate limits to failed authentication attempts
  • Use progressive delays, temporary lockouts, or other carefully bounded backoff mechanisms
  • Place the Publish Service behind an authenticated reverse proxy, VPN, or trusted network boundary where appropriate
  • Require strong, unique credentials for named publish-viewer accounts
  • Minimize account privileges and published content scope
  • Monitor and restrict unnecessary network access to the service listener
  • Avoid relying on Basic Auth as the only control when stronger authentication layers are available

How teams detect issues like this

Organizations commonly detect this weakness through:

  • Static analysis and code review searches for authentication handlers without counters, throttling, lockout, or backoff logic
  • Review of routes that accept repeated credential failures without per-account or per-client controls
  • Runtime monitoring for bursts of failed Basic Auth requests and repeated attempts against the same account
  • Network policy checks confirming that publishing listeners are not broadly exposed
  • Automated security review tools and authentication policy tests that verify excessive-attempt protections

Sources

SourceLink
github.comgithub.com/siyuan-note/siyuan/security/advisories/GHSA-phg7-xcr4-q5wg
vulncheck.comvulncheck.com/advisories/siyuan-before-brute-force-authentication-via-publish-service

Frequently asked

questions

Yes. An attacker generally needs only network reachability to the Publish Service listener; prior authentication is not required.

The attacker must target a named publish-viewer account, but does not need valid credentials before beginning password-guessing attempts.

Enforce layered protections such as per-account throttling, progressive backoff or bounded lockouts, strong credentials, and restricted network exposure.

Include excessive-authentication-attempt tests in code review and security testing, and continuously monitor failed-login patterns at both the application and network layers.

Find out what's already
exploitable in your codebase.