# CVE-2026-72798: SiYuan before v3.7.4 Information Disclosure via renderAttributeView

> Attackers can access sensitive content from hidden or password-protected databases in SiYuan by exploiting improper filtering in renderAttributeView.

- **Severity:** Critical 9.2 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 12 Aug 2026
- **Updated:** 14 Aug 2026
- **Also known as:** GHSA-mfrj-v65r-979c, GO-2026-6415

## What is CVE-2026-72798?

CVE-2026-72798 is a critical 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 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.

Weakness: CWE-862 (Missing Authorization)

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

3 open source packages ship an affected version, including github.com/siyuan-note/siyuan/kernel.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/siyuan-note/siyuan/kernel` | Go | All versions | 0.0.0-20260724121519-426991d155c0 |
| `github.com/siyuan-note/siyuan/kernel` | Go | All versions | 0.0.0-20260724121519-426991d155c0 |
| `github.com/siyuan-note/siyuan/kernel` | Go | All versions | 0.0.0-20260724121519-426991d155c0 |

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

Upgrade github.com/siyuan-note/siyuan/kernel to 0.0.0-20260724121519-426991d155c0 or later.

## Is CVE-2026-72798 being exploited?

There is no known exploitation of CVE-2026-72798 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-72798 is a critical 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: There is no known exploitation of CVE-2026-72798 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/siyuan-note/siyuan/kernel (Go): affected all versions; fixed in 0.0.0-20260724121519-426991d155c0
- github.com/siyuan-note/siyuan/kernel (Go): affected all versions; fixed in 0.0.0-20260724121519-426991d155c0
- github.com/siyuan-note/siyuan/kernel (Go): affected all versions; fixed in 0.0.0-20260724121519-426991d155c0

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-72798/ (Markdown: https://insights.sbomify.com/CVE-2026-72798/index.md)
```

## Sources

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

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