ZDF
Sign inSign up

Vulnerabilities

Security incident · CVE-2026-72791

SiYuan: Database view structure (all view names, layout types and per-field visibility) is returned to anonymous readers by /api/av/getAttributeViewFieldViews

Published Sep 8, 2026 · catalog updated Oct 30, 2026 · SiYuan: Database view structure

Last checked Oct 31, 2026. A connected source was read within the last 7 days.

Check if you run it

No confirmed exploitation is on record for CVE-2026-72791. EPSS is 0.33%. Act only if a listed version of SiYuan: Database view structure is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (SiYuan: Database view structure).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
Medium5.8
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.33%
Remediation
Advisory link
Affected products
Go github.com/siyuan-note/siyuan/kernel

### Scope note (please read first) This endpoint does not exist in v3.7.3 or on master. It was introduced on the development branch by commit ("Improve database field visibility across views", #11020) and is live on , so it will ship in v3.7.4 unless gated first. No released stable version is affected. ### Summary is registered with only and applies no publish-access filtering. Given a database , it returns the complete view structure of that database: every view's name, icon, layout type and the per-field flag, regardless of whether the caller is authorized to see that database or those views. The route registered immediately before it, , does gate reader roles. ### Details | Item | Detail | |---|---| | Route | → → | | Middleware | only, no , no | | Guard in handler | None. Greps for , and all return zero matches | | Exposed | For each entry in : , , , , and the flag for the requested field | | Introduced by | (feature), dev branch only | **The leak path.** The handler binds and , validating them against the ID pattern only, then calls . That function calls , which reads the database's storage file directly by identifier. There is no ownership check and no publish-access check anywhere on the path. The result is a per-view record for every view the database defines. What a reader learns is author-written: view names are typed by the user, and layout type distinguishes a table from a gallery or kanban. The flag additionally reveals, per view, which fields the author chose to conceal. **Guarded sibling, one route earlier.** ( ) is also reader-reachable and does gate: The new route at 530 applies nothing equivalent. This is worth flagging as more than an isolated omission. added a new reader-reachable attribute-view endpoint during the same development cycle in which the surrounding attribute-view endpoints were being hardened. The same pattern produced an earlier exposure: , which added encrypted-notebook unlock status for plugin consumption, created a reader-reachab

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • Go github.com/siyuan-note/siyuan/kernel0 → 0.0.0-20260726004013-64c26e74bb82

How to fix CVE-2026-72791

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-72791. EPSS is 0.33%. Act only if a listed version of SiYuan: Database view structure is installed.

Which versions are affected?

Compare what you have installed with 0 → 0.0.0-20260726004013-64c26e74bb82. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-862: Missing Authorization. EPSS 0.33%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Sep 8, 2026 · Go Vulnerability Database

    Detected

    ### Scope note (please read first) This endpoint does not exist in v3.7.3 or on master. It was introduced on the development branch by commit ("Improve database field visibility across views", #11020) and is live on , so it will ship in v3.7.4 unless gated first. No released stable version is affected. ### Summary is registered with only and applies no publish-access filtering. Given a database ,

  2. Oct 30, 2026 · Go Vulnerability Database

    Fix available

    github.com/siyuan-note/siyuan/kernel fixed in 0.0.0-20260726004013-64c26e74bb82

  3. Oct 30, 2026 · Go Vulnerability Database

    Fix available

    github.com/siyuan-note/siyuan/kernel fixed in 0.0.0-20260726004013-64c26e74bb82

  4. Oct 30, 2026 · Go Vulnerability Database

    Updated

    ### Scope note (please read first) This endpoint does not exist in v3.7.3 or on master. It was introduced on the development branch by commit ("Improve database field visibility across views", #11020) and is live on , so it will ship in v3.7.4 unless gated first. No released stable version is affected. ### Summary is registered with only and applies no publish-access filtering. Given a database ,

Sources

  • CVE.orgVulnerability recordCVE-2026-72791

    Official CVE identifier

    cve.org
  • Go Vulnerability DatabasePackage advisoryGHSA-57v5-wqx3-cgj4

    SiYuan: Database view structure (all view names, layout types and per-field visibility) is returned to anonymous readers by /api/av/getAttributeViewFieldViews

    osv.dev
  • Go Vulnerability DatabasePackage advisoryGO-2026-6430

    SiYuan: Database view structure (all view names, layout types and per-field visibility) is returned to anonymous readers by /api/av/getAttributeViewFieldViews in github.com/siyuan-note/siyuan/kernel

    osv.dev

References

Freshness

Last verified in this catalog Oct 30, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • Go Vulnerability DatabaseOct 31, 2026
  • Go Vulnerability DatabaseOct 31, 2026
  • CVE.orgOct 30, 2026