Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-68584 – Authentication Bypass – SiYuan (siyuan-note/siyuan) before v3.7.3

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-68584 is an authentication bypass vulnerability (CWE-288, Authentication Bypass Using an Alternate Path or Channel) in SiYuan Note’s publish mode. Multiple content-returning endpoints fail to enforce the publish-password check that protects the primary document endpoint, allowing an unauthenticated remote attacker to read password-protected document content. It affects all versions before v3.7.3 and is rated Critical (CVSS v4.0 9.2).

Technical details

  • Root cause: While the primary getDoc endpoint enforces publish-password verification through FilterContentByPublishAccess, alternate content-returning endpoints (getHeadingChildrenDOM, getHeadingDeleteTransaction, getHeadingLevelTransaction, getHeadingInsertTransaction, getBacklinkDoc, getBackmentionDoc) omit this control.
  • Trigger conditions: SiYuan running in publish mode with password-protected documents exposed to the network.
  • Attack vector: Network, unauthenticated. An anonymous user retrieves document metadata (listed despite password protection), extracts block IDs from an endpoint that filters content but retains identifiers, then queries the unprotected endpoints with those IDs to retrieve rendered content.
  • Impact: Confidentiality breach — full disclosure of protected document content, bypassing the intended password gating. No integrity or availability impact.

Affected software

  • SiYuan (siyuan-note/siyuan) — all versions before v3.7.3 (kernel v3.7.2 and earlier).

Severity

  • CVSS v4.0 base score: 9.2 (Critical) — CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N
  • CVSS v3.1 base score: 8.6 (High) — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N

Mitigation and recommended actions

  • Immediate: Upgrade to SiYuan v3.7.3 or later, which applies password verification to the affected content endpoints.
  • If no patch: Avoid exposing publish mode to untrusted networks; place the publish service behind an authenticating reverse proxy or VPN, and restrict network access to trusted clients until the update is applied.

How IONIX identifies potentially affected assets

IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Page title: Access Authorization - SiYuan, 思源笔记
  • Raw response body: exitSiYuan, b3log.org/siyuan

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge