# CVE-2026-59853: Missing authorization in siyuan

> A missing authorization check in SiYuan's publish mode allows readers to access private saved search criteria and document metadata.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Jul 2026
- **Updated:** 10 Jul 2026
- **Also known as:** GHSA-px3c-cf92-9g83

## What is CVE-2026-59853?

CVE-2026-59853 is a medium-severity missing authorization vulnerability in siyuan-note siyuan, published on 9 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

SiYuan is an open-source personal knowledge management system. Prior to 3.7.1, the /api/storage/getCriteria endpoint returns saved search criteria from data/storage/criteria.json without the publish-access filtering used by sibling storage endpoints, allowing a publish-mode Reader to read private document paths, notebook, document, and block IDs, and search and replace keywords for unpublished documents. This issue is fixed in versions 3.7.1.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-59853 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-59853 is a medium-severity missing authorization vulnerability in siyuan-note siyuan, published on 9 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-59853 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-59853/ (Markdown: https://insights.sbomify.com/CVE-2026-59853/index.md)
```

## Sources

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

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