# CVE-2026-104410: SiYuan before 3.8.5 Information Disclosure via /api/export/preview

> Attackers can read password-protected database rows via the export preview endpoint in SiYuan, exposing sensitive data to unauthorized users.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/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:** 2 Oct 2026
- **Updated:** 2 Oct 2026
- **Also known as:** GHSA-778g-gq49-fxxj, GHSA-84pg-x94v-x3xr

## What is CVE-2026-104410?

CVE-2026-104410 is a high-severity missing authorization vulnerability in siyuan-note siyuan, published on 2 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SiYuan before 3.8.5 contains an information disclosure vulnerability that allows publish readers to read password-protected and publish-disabled database rows via the /api/export/preview endpoint. Attackers can request an export preview of a public document embedding a database view to obtain protected rows' primary-key text and cell values.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-104410 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-104410 is a high-severity missing authorization vulnerability in siyuan-note siyuan, published on 2 Oct 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-104410 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-104410/ (Markdown: https://insights.sbomify.com/CVE-2026-104410/index.md)
```

## Sources

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

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