# CVE-2026-73608: SiYuan v3.7.4-alpha.2 Authorization Bypass via getAttributeViewSearchTarget

> An anonymous attacker can bypass authorization checks to read restricted database rows in SiYuan's development branch via a specific API endpoint.

- **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:** No
- **Published:** 13 Aug 2026
- **Updated:** 29 Oct 2026

## What is CVE-2026-73608?

CVE-2026-73608 is a critical missing authorization 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's development branch (endpoint introduced by commit 9b8e8956f, not present in v3.7.3 or master, patched in v3.7.4-alpha.3) contains a missing-authorization vulnerability in the /api/av/getAttributeViewSearchTarget endpoint. The route is registered with CheckAuth only and performs no authorization checks (no CheckReadonly, no publish-access or encrypted-notebook gating). Given a database identifier taken from a published page and a keyword, an anonymous reader can query the endpoint to retrieve matching database row content, including rows that publish filters (FilterAttributeViewByPublishAccess) would otherwise withhold. No released stable version is affected.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-73608 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-73608 is a critical missing authorization 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-73608 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-73608/ (Markdown: https://insights.sbomify.com/CVE-2026-73608/index.md)
```

## Sources

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

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