# SiYuan: getAttributeViewSearchTarget returns database row content to anonymous readers with no publish-access check, reopening the class closed one day earlier at the adjacent route Advisory record · `GHSA-9cqf-hhrq-7v45` - **Identifiers:** `GHSA-9cqf-hhrq-7v45` · `CVE-2026-73608` · `GO-2026-6632` - **State:** Confirmed - **Severity:** CVSS 9.2 Critical - **Critical:** Yes: CVSS 9+ - **Weakness (CWE):** [CWE-862](https://cwe.mitre.org/data/definitions/862.html) - **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md) - **Published:** 1 Oct 2026 - **Updated:** 30 Oct 2026 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 1 Oct 2026, 16:24 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Critical Critical, because: - CVSS score 9.2: 9.0 or more. How we decide what’s critical: ## Affected packages - `github.com/siyuan-note/siyuan/kernel` (Go): affected `>=0.0.0-20260726161145-9b8e8956f997, <0.0.0-20260812083335-251596fc0de2`; fixed in `0.0.0-20260812083335-251596fc0de2` ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > GHSA-9cqf-hhrq-7v45 affects the SiYuan kernel Go module on development builds from version 0.0.0-20260726161145-9b8e8956f997 up to, but not including, 0.0.0-20260812083335-251596fc0de2, where the fix is listed. The /api/av/getAttributeViewSearchTarget endpoint has no read-only or publish-access check, so an anonymous reader in publish mode can search database rows, including rows the publish filters hide, and read matching content. Upgrade to 0.0.0-20260812083335-251596fc0de2 or later. The source says no released stable version is affected. Written 1 Nov 2026. ## Not analysed yet We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check. ## Severity and exploitation - 9.2 Critical, CVSS 4.0: `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`, from CNA (VulnCheck) - **CISA KEV:** Not listed. - **EPSS:** 0.0031, the 23rd percentile, on 7 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days. ## Timeline - 31 Oct 2026, 14:11 UTC: First seen by agentprime - 31 Oct 2026, 14:11 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-9cqf-hhrq-7v45) ## Sources - [GitHub Advisory Database: GHSA-9cqf-hhrq-7v45](https://github.com/advisories/GHSA-9cqf-hhrq-7v45) - [OSV: GHSA-9cqf-hhrq-7v45](https://osv.dev/vulnerability/GHSA-9cqf-hhrq-7v45) - - - - Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code. ## Check whether this affects you A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet. - With the agentprime MCP server (), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .