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

Back
New CVE Detected

CVE-2026-72798 – Information Disclosure via Missing Authorization – SiYuan Note before v3.7.4

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

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-72798 is an information disclosure vulnerability in SiYuan Note, an open-source personal knowledge management system, caused by improper access-control filtering in the renderAttributeView function. The flaw allows anonymous or unauthenticated readers of a published SiYuan workspace to retrieve Relation and Rollup cell contents originating from hidden, publish-forbidden, or password-protected databases. It affects all SiYuan versions before v3.7.4 and carries a CVSS v3.1 base score of 8.6 (High), with a CVSS v4.0 score of 9.2 (Critical).

Technical details

  • Root cause: the publish-access filter in renderAttributeView evaluates row accessibility only against the first cell (row.Cells[0].Value.Block) of each row, without validating the contents of Relation or Rollup cells that mirror data pulled in from a separate, restricted database.
  • A second contributing flaw: when a database’s first column holds a non-block type (e.g., text or relation) or the row lacks a block reference, the accessibility check is skipped entirely, so rows are returned with no filtering applied.
  • Trigger conditions: a SiYuan instance running the Publish server with a database that is published/public but has a Relation or Rollup column pointing to a hidden, publish-forbidden, or password-protected database — or a published database whose first column is not a block reference.
  • Attack vector: Network, no authentication or user interaction required; an attacker queries the public/published database API endpoint directly.
  • Impact: confidentiality loss — block text, titles, and column values from restricted databases can be exposed to anonymous readers; no impact to integrity or availability.
  • Relevant code paths: kernel/api/av.go (applies FilterViewByPublishAccess), kernel/model/publish_access.go (row filtering logic), and kernel/model/attribute_view.go (populates relation/rollup content from other databases).

Affected software

  • SiYuan (siyuan-note/siyuan), gomod package github.com/siyuan-note/siyuan/kernel
  • All versions ≤ v3.7.2 (and any version prior to the fix release)
  • Fixed in v3.7.4

Severity

  • 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
  • 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

Mitigation and recommended actions

  • Immediate: upgrade SiYuan to v3.7.4 or later, which validates Relation and Rollup contents against publish-access rules and closes the fail-open path for non-block first columns.
  • If unable to patch immediately: disable or restrict the Publish server’s anonymous/public access mode, avoid publishing databases that contain Relation or Rollup columns referencing hidden or password-protected databases, and restrict network access to the publish endpoint (e.g., via firewall/VPN) until patched.

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