/

CVE-2026-73054

Severity:

HIGH RISK

(7.5)

WebSocket Auth Bypass (CWE-287) in SiYuan Endpoint

CVE-2026-73054

Deferred

Vulnerability type

Category:

Authentication Bypass

CWE:

CWE-287

Impact:

Unauthorized Information Disclosure

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 versions before 3.7.4 contain an authentication bypass in a WebSocket endpoint caused by inconsistent parsing of duplicated query parameters. An unauthenticated attacker may exploit this behavior to bypass access-code validation and receive live kernel event data, including document identifiers, titles, and operation logs.

Affected context

The vulnerability occurs in SiYuan deployments that expose the affected WebSocket endpoint and rely on query parameters for access-code validation and session quarantine decisions. Risk is increased when the endpoint is reachable by untrusted clients and the application processes duplicated query parameters differently across authentication-related checks.

Exploit preconditions

  • Attack surface: The SiYuan WebSocket endpoint
  • Required access: Network access to the endpoint; valid authentication is not necessarily required
  • Trigger point: WebSocket connection handling involving duplicated query parameters
  • Why exploitation is possible: Authentication exemption and session quarantine logic interpret the same query parameters inconsistently, allowing access-code validation to be bypassed

Why this happens

The underlying defect is inconsistent normalization and interpretation of repeated query parameters across security-sensitive request checks. One component may use one occurrence of a parameter while another component uses a different occurrence, causing authentication decisions to diverge.

This behavior maps to CWE-287: Improper Authentication, because the application does not consistently establish that a client is authorized before granting access to protected WebSocket data.

Potential impact

  • An unauthenticated user may receive live kernel event streams
  • Document identifiers and titles could be disclosed
  • Operation logs may be exposed to unauthorized parties
  • Attackers could use disclosed metadata to improve targeting of the SiYuan instance
  • Security monitoring and privacy expectations could be weakened

General mitigation guidance

Mitigation generally focuses on making authentication decisions consistent, deterministic, and independent of ambiguous parameter representations.

Common defensive patterns include:

  • Rejecting duplicate security-sensitive query parameters rather than selecting one implicitly
  • Canonicalizing request parameters once before authentication and authorization checks
  • Applying the same parsed representation to access-code, session, and quarantine logic
  • Requiring authentication through a secure, unambiguous mechanism for WebSocket connections
  • Limiting WebSocket exposure to trusted networks or authenticated reverse-proxy paths
  • Applying least-privilege access to event streams and minimizing sensitive data in operational messages

How teams detect issues like this

Detection approaches may include:

  • Static analysis and code review for repeated query-parameter access in authentication or authorization paths
  • Tests covering duplicate, reordered, empty, and conflicting security-related parameters
  • Policy checks requiring canonical request parsing before security decisions
  • Web application firewall or gateway rules that reject ambiguous duplicate parameters where compatible
  • Monitoring for unauthenticated WebSocket connections and unusual subscriptions to kernel event streams
  • Automated security review tools that flag inconsistent parameter handling across request-validation stages

Sources

SourceLink
github.comgithub.com/siyuan-note/siyuan/security/advisories/GHSA-c8w8-3pqp-wr83
vulncheck.comvulncheck.com/advisories/siyuan-before-authentication-bypass-via-websocket

Frequently asked

questions

Yes. It may be remotely exploitable when an attacker can reach the affected WebSocket endpoint over the network and the deployment does not otherwise restrict access.

The described bypass is intended to avoid normal access-code validation, so valid application credentials may not be required. Network reachability and endpoint exposure remain important conditions.

Use consistent, canonical parsing for all security-sensitive parameters and reject ambiguous duplicate values before authentication or authorization decisions are made.

Add duplicate-parameter and parser-differential tests, enforce authentication consistently across WebSocket lifecycle checks, minimize event-stream data exposure, and monitor unauthenticated connection attempts.

Find out what's already
exploitable in your codebase.