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

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.8 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N

EPSS

• CVE-2026-72791: 0.33% estimated exploitation activity in the next 30 days; percentile 25.60 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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 `acfc02ee8` ("Improve database field visibility across views", #11020) and is live on `v3.7.4-alpha.1`, so it will ship in v3.7.4 unless gated first. No released stable version is affected.

Summary `/api/av/getAttributeViewFieldViews` is registered with `CheckAuth` only and applies no publish-access filtering. Given a database `avID`, it returns the complete view structure of that database: every view's name, icon, layout type and the per-field `Hidden` flag, regardless of whether the caller is authorized to see that database or those views. The route registered immediately before it, `getAttributeViewKeys`, does gate reader roles.

Details | Item | Detail | |---|---| | Route | `kernel/api/router.go:530` `POST /api/av/getAttributeViewFieldViews` → `model.CheckAuth` → `getAttributeViewFieldViews` | | Middleware | `CheckAuth` only, no…

Published by the source

8 Sep 2026, 17:53 UTC

Last modified by the source

30 Oct 2026, 10:55 UTC

Source last checked

31 Oct 2026, 06:45 UTC

1. Revision 5 · amended · 31 Oct 2026

   Amended from osv record GO-2026-6430

2. Revision 4 · amended · 31 Oct 2026

   Amended from osv record GHSA-57v5-wqx3-cgj4

3. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-57v5-wqx3-cgj4

4. Revision 2 · amended · 24 Oct 2026

   Amended from osv record GO-2026-6430

5. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-57v5-wqx3-cgj4

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-72791

Advisory: SiYuan: Database view structure (all view names, layout types and per-field visibility) is returned to anonymous readers by /api/av/getAttributeViewFieldViews
IDs: CVE-2026-72791, GHSA-57v5-wqx3-cgj4
Record: https://patchnext.com/advisories/ghsa-57v5-wqx3-cgj4 (revision 5, source checked 31 Oct 2026, 06:45 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/siyuan-note/siyuan/kernel 0.0.0-20260726004013-64c26e74bb82. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/siyuan-note/siyuan/kernel: affected < 0.0.0-20260726004013-64c26e74bb82; fixed in 0.0.0-20260726004013-64c26e74bb82

## Suggested inspection (read-only)
- Go github.com/siyuan-note/siyuan/kernel: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/siyuan-note/siyuan/kernel.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-57v5-wqx3-cgj4 (OSV record GHSA-57v5-wqx3-cgj4 lists affected ranges: Go github.com/siyuan-note/siyuan/kernel >=0 <0.0.0-20260726004013-64c26e74bb82 (fixed))
- Verified: https://osv.dev/vulnerability/GO-2026-6430 (OSV record GO-2026-6430 lists affected ranges: Go github.com/siyuan-note/siyuan/kernel >=0 <0.0.0-20260726004013-64c26e74bb82 (fixed))
- Verified: https://github.com/advisories/GHSA-57v5-wqx3-cgj4 (GitHub-reviewed advisory GHSA-57v5-wqx3-cgj4 lists affected ranges: Go github.com/siyuan-note/siyuan/kernel >=0 <0.0.0-20260726004013-64c26e74bb82)

Commands are suggestions: review each one before running it.