# CVE-2026-72791: SiYuan v3.7.4-alpha.1 Information Disclosure via getAttributeViewFieldViews

> Attackers with reader access can retrieve full database view structures, including hidden fields, from any database in SiYuan.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Aug 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-xf8j-hfm6-vc9v

## What is CVE-2026-72791?

CVE-2026-72791 is a medium-severity missing authorization vulnerability in siyuan-note siyuan, published on 12 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SiYuan v3.7.4-alpha.1 (a pre-release; the endpoint does not exist in stable v3.7.3 or earlier) contains an information disclosure vulnerability in the /api/av/getAttributeViewFieldViews endpoint. The route is registered with CheckAuth only and applies no publish-access filtering, so reader-role callers can retrieve the complete database view structure — every view's name, icon, layout type, and per-field Hidden flag — for any database whose avID is supplied, regardless of authorization. The issue was introduced by commit acfc02ee8 and fixed in v3.7.4-alpha.2.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-72791?


## How do I fix CVE-2026-72791?

No fix has been published for CVE-2026-72791 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-72791 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-72791 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-72791 and fix it if it is affected.

What it is: CVE-2026-72791 is a medium-severity missing authorization vulnerability in siyuan-note siyuan, published on 12 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-72791 exists.

Affected product: siyuan-note siyuan. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-72791/ (Markdown: https://insights.sbomify.com/CVE-2026-72791/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-72791
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-72791
- OSV: https://osv.dev/vulnerability/CVE-2026-72791

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-72791/
Summaries are generated and may contain mistakes; the official description above is the record.