# CVE-2026-103763: SiYuan before v3.8.5 Information Disclosure via /api/notebook/getNotebookInfo

> Attackers can access metadata of hidden documents in published notebooks via the getNotebookInfo API endpoint.

- **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:** 2 Oct 2026
- **Updated:** 2 Oct 2026
- **Also known as:** GHSA-ccxp-q3vg-jvgj, GHSA-cj7w-46vh-93h9

## What is CVE-2026-103763?

CVE-2026-103763 is a medium-severity 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 v3.8.5 contains an information disclosure vulnerability that allows read-only publish readers to learn metadata of publish-excluded documents through the getNotebookInfo endpoint. Attackers, including anonymous visitors when no reader password is set, can query publish-visible notebooks to obtain document count, size and modification timestamps of hidden documents.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

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

## Is CVE-2026-103763 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-103763 is a medium-severity 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-103763 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-103763/ (Markdown: https://insights.sbomify.com/CVE-2026-103763/index.md)
```

## Sources

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

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