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

New CVE Detected

CVE-2026-72795 – Information Disclosure (Unauthorized Access to Private/Password-Protected Documents

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

Summary

CVE-2026-72795 is an information disclosure vulnerability in SiYuan Note (github.com/siyuan-note/siyuan/kernel) affecting all versions before v3.7.4. The kernel’s getBlockDOMWithEmbed and getBlockDOMsWithEmbed API endpoints fail to filter embedded block content by publish access, allowing anonymous or low-privilege readers to view content from unpublished, hidden, password-protected, or otherwise restricted documents. The issue is rated CRITICAL, with a published CVSS v4.0 base score of 9.2.

Technical details

  • Root cause: the internal function resolveEmbedContentInBox retrieves and inlines embedded block content without applying publish-access filtering, even though it applies such checks to the top-level requested block.
  • The sibling endpoint getEmbedBlock correctly applies FilterEmbedBlocksByPublishAccess, but the DOM-rendering endpoints getBlockDOMWithEmbed and getBlockDOMsWithEmbed do not.
  • Trigger condition: a reader requests any legitimately published document that contains an embed/transclusion query; embedded blocks matched by that query are returned regardless of their own access restrictions.
  • Attack vector: network, no authentication or special privileges required, no user interaction beyond normal viewing of a published document.
  • Impact: disclosure of confidential content from restricted, password-protected, or unpublished documents; workspace-spanning embed queries in aggregation-style published pages can expose substantial private content passively.

Affected software

  • SiYuan (github.com/siyuan-note/siyuan/kernel) — all versions ≤ v3.7.2 / prior to v3.7.4

Severity

  • CVSS v4.0: 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: 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 SiYuan to v3.7.4 or later, where publish-access filtering has been applied to the affected endpoints.
  • If patching is not immediately possible: disable or restrict public/publish-mode access to SiYuan workspaces, and avoid publishing documents that contain embed/transclusion queries referencing restricted or password-protected blocks until patched.

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

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

Subscribe to Threat Center RSS

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

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge