Which versions of SiYuan are affected by CVE-2026-72798?

SiYuan note-taking application versions before 3.7.4 expose sensitive data stored in password-protected databases to unauthenticated attackers through published workspace attribute views.. A patch is available.

Is there a public PoC exploit available for CVE-2026-72798?

Yes, a public proof-of-concept exploit is available for CVE-2026-72798. Prioritise patching immediately. EPSS: 0.3%.

How to fix or mitigate CVE-2026-72798?

Within 24 hours, immediately audit all published SiYuan workspaces containing sensitive data and disable public workspace sharing to prevent further exposure. Within 7 days, implement network-level access controls restricting external access to SiYuan instances and review server logs for unauthorized attribute view requests or suspicious IP addresses accessing published workspaces. Within 30 days, upgrade to SiYuan v3.7.4 or later once released, conduct a comprehensive data breach assessment to identify potentially exfiltrated records, and establish technical controls enforcing authentication for all attribute view access.

SiYuan CVE-2026-72798

Q: What is the CVSS score of CVE-2026-72798?

CVE-2026-72798 has a CVSS 4.0 base score of 9.2 (Critical). CVSS vector: 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. EPSS exploitation probability: 0.3%.

EUVD-2026-57458 CRITICAL

Missing Authorization (CWE-862)

2026-08-12 VulnCheck

GHSA-mfrj-v65r-979c

GHSA-mg8q-52j3-w5f8

Authentication Bypass Siyuan Siyuan Note

9.2

CVSS 4.0 · Vendor: VulnCheck

Severity by source

Vendor (VulnCheck) PRIMARY

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

vuln.today AI

8.6 HIGH

Remote, unauthenticated, low-complexity read of protected data across a trust boundary gives AV:N/AC:L/PR:N/UI:N with S:C and C:H; no integrity or availability impact.

3.1 AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N

4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N

Primary rating from Vendor (VulnCheck).

CVSS VectorVendor: VulnCheck

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Lifecycle Timeline

Patch available

Aug 12, 2026 - 20:03 EUVD

Analysis Generated

Aug 12, 2026 - 19:56 vuln.today

CVE Published

Aug 12, 2026 - 19:07 cve.org

CRITICAL 9.2

DescriptionCVE.org

SiYuan versions before v3.7.4 fail to properly filter related-database content in renderAttributeView, allowing anonymous readers to access Relation and Rollup cell contents from hidden or password-protected databases. Attackers can request published databases that relate to restricted databases to retrieve sensitive content, or bypass row filtering entirely when the first column is a non-block type.

AnalysisAI

Sensitive data disclosure in SiYuan note-taking application before v3.7.4 lets anonymous readers of a published workspace pull Relation and Rollup cell contents out of hidden or password-protected databases. Because renderAttributeView does not re-check authorization on the related database, an unauthenticated visitor can request a published attribute view that references a restricted database and read its protected values, and can bypass row-level filtering entirely when the first column is a non-block type. Reported by VulnCheck with a CVSS 4.0 base score of 9.2; no public exploit identified at time of analysis.

Technical ContextAI

SiYuan is an open-source, self-hostable personal knowledge-management and Markdown note-taking application whose 'attribute views' provide Notion-style database tables. Relation columns link one database to another and Rollup columns aggregate values pulled across that link. The flaw is in the renderAttributeView routine, which resolves and renders those related-database values without re-applying the access controls (hidden/password protection and row filters) that the referenced database is supposed to enforce. This is a classic CWE-862 Missing Authorization defect: an authorization decision that is enforced when the database is accessed directly is silently skipped on the cross-reference rendering path, so data crosses a trust boundary. A secondary logic error causes row-filtering to be bypassed when the first column of the view is a non-block type. The affected component is siyuan-note:siyuan (all versions prior to v3.7.4).

RemediationAI

Upgrade to SiYuan v3.7.4 or later, which corrects the authorization checks in renderAttributeView (Vendor-released patch: v3.7.4), as documented in the vendor advisory GHSA-mfrj-v65r-979c (https://github.com/siyuan-note/siyuan/security/advisories/GHSA-mfrj-v65r-979c). Until the upgrade is applied, reduce exposure by not publishing attribute views that contain Relation or Rollup columns pointing at hidden or password-protected databases, and by removing anonymous/public read access to the publishing endpoint or placing it behind authentication or a network restriction - the trade-off is that legitimate anonymous readers lose access to the published workspace. As an additional interim measure, avoid using non-block first columns in views that rely on row filtering to withhold sensitive rows, since that configuration defeats the filter; note this changes how affected tables render and is only a stopgap until v3.7.4 is deployed.