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

Back
New CVE Detected

CVE-2026-74906 – Unauthenticated Disclosure of Publish-Restricted Content – SiYuan Note before v3.7.

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

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-74906 is an incorrect authorization (CWE-863) vulnerability affecting SiYuan Note, a self-hosted personal knowledge management and note-taking application, in all versions prior to 3.7.4. Eight reader-facing endpoints in SiYuan’s Publish service filter content using a document visibility list instead of the intended disable (access-control) list, allowing unauthenticated remote visitors to discover and read the contents of documents that workspace owners explicitly marked as forbidden from publishing. The flaw carries a CVSS v4.0 base score of 8.7 (High), reflecting a network-exploitable, no-authentication confidentiality breach.

Technical details

  • Root cause: SiYuan’s publish-access model maintains two independent controls per document (PublishAccessItem): Visible (controls whether a document appears in navigation) and Disable (controls whether the document’s content can actually be accessed). The eight affected endpoints incorrectly call GetInvisiblePublishAccess() to filter results instead of GetDisablePublishAccess(), so documents with Disable=true but Visible=true remain reachable through these endpoints.
  • Trigger conditions: A SiYuan workspace must have its Publish service enabled (i.e., publicly exposed publish/kernel endpoints), with at least one document flagged as disabled/forbidden from publishing while still marked visible in navigation.
  • Attack vector: Network-based, unauthenticated. No user interaction or privileges are required — an anonymous visitor can send requests directly to the affected API endpoints.
  • Impact: Confidentiality breach only (no integrity or availability impact). Attackers can read content the workspace owner intended to keep private, via full-text search results, backlinks, asset content, saved search criteria, recent documents lists, the document graph, and tag listings.
  • Affected endpoints:
    • POST /api/filetree/searchDocs
    • POST /api/ref/getBacklink and getBacklink2
    • POST /api/search/getAssetContent, getAssetContentByPath, fullTextSearchAssetContent
    • POST /api/storage/getCriteria
    • POST /api/storage/getRecentDocs
    • POST /api/graph/getGraph and getLocalGraph
    • POST /api/tag/getTag

Affected software

  • Product: SiYuan (siyuan-note / B3log), Go module github.com/siyuan-note/siyuan/kernel
  • Affected versions: All versions prior to 3.7.4 (confirmed vulnerable: v3.7.3)
  • Fixed version: 3.7.4 and later

Severity

  • CVSS v4.0: 8.7 (High) — CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
  • CVSS v3.1: 7.5 (High) — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
  • CWE: CWE-863 (Incorrect Authorization)

Mitigation and recommended actions

  • Immediate: Upgrade SiYuan to version 3.7.4 or later, which fixes the affected endpoints to correctly filter using the disable/access-control list rather than the visibility list.
  • If immediate patching is not possible:
    • Restrict or disable public exposure of the SiYuan Publish service until patched.
    • Audit documents currently marked as "forbidden from publishing" (Disable) and verify no sensitive content was exposed via the affected search, backlink, asset, criteria, recent-documents, graph, or tag endpoints while the instance was internet-exposed.
    • Place the publish/kernel endpoints behind network-level access controls (e.g., allow-listing, VPN, or reverse-proxy authentication) as a compensating control until the upgrade is applied.

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