# CVE-2026-73610: SiYuan before v3.7.4 Information Disclosure via Local Storage

> Unauthenticated attackers can retrieve sensitive local storage data, including history and private identifiers, from SiYuan note-taking application.

- **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:** 13 Aug 2026
- **Updated:** 14 Aug 2026
- **Also known as:** GHSA-8j5p-6pf5-6pqc

## What is CVE-2026-73610?

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

### Official description

SiYuan before v3.7.4 contains an information disclosure vulnerability in the local storage filter that returns the administrator's entire storage map with only three keys sanitized. Unauthenticated attackers or publish readers can retrieve closed-tab history, search keywords, private document identifiers, and expanded folder paths by calling the getLocalStorage endpoint.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2026-73610 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-73610 is a medium-severity vulnerability in siyuan-note siyuan, published on 13 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-73610 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-73610/ (Markdown: https://insights.sbomify.com/CVE-2026-73610/index.md)
```

## Sources

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

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