# CVE-2026-34453: SiYuan: Unauthenticated Access to Password-Protected Bookmarks via /api/bookmark/getBookmark > Unauthenticated users can read password-protected bookmarked content in SiYuan's publish service due to broken access control. - **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 31 Mar 2026 - **Updated:** 1 Apr 2026 - **Also known as:** GHSA-c77m-r996-jr3q, GO-2026-5318 ## What is CVE-2026-34453? CVE-2026-34453 is a high-severity missing authorization vulnerability in B3log Siyuan, published on 31 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description SiYuan is a personal knowledge management system. Prior to version 3.6.2, the publish service exposes bookmarked blocks from password-protected documents to unauthenticated visitors. In publish/read-only mode, /api/bookmark/getBookmark filters bookmark results by calling FilterBlocksByPublishAccess(nil, ...). Because the filter treats a nil context as authorized, it skips the publish password check and returns bookmarked blocks from documents configured as Protected. As a result, anyone who can access the publish service can retrieve content from protected documents without providing the required password, as long as at least one block in the document is bookmarked. This issue has been patched in version 3.6.2. Weakness: CWE-863 (Incorrect Authorization) ## Which versions are affected by CVE-2026-34453? 3 open source packages ship an affected version, including github.com/siyuan-note/siyuan/kernel. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/siyuan-note/siyuan/kernel` | Go | All versions | None | | `github.com/siyuan-note/siyuan/kernel` | Go | All versions | 3.6.2 | | `github.com/siyuan-note/siyuan/kernel` | Go | All versions | 3.6.2 | Products: B3log Siyuan. ## How do I fix CVE-2026-34453? Upgrade github.com/siyuan-note/siyuan/kernel to 3.6.2 or later. ## Is CVE-2026-34453 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-34453 exists. Public exploit code: - SiYuan <= v3.6.1 - Bookmark Data Disclosure (nuclei): http/cves/2026/CVE-2026-34453.yaml ## Other vulnerabilities in B3log Siyuan - [CVE-2026-32938](https://insights.sbomify.com/CVE-2026-32938/): SiYuan has an Arbitrary File Read in its Desktop Publish Service (critical 9.9) - [CVE-2026-33669](https://insights.sbomify.com/CVE-2026-33669/): SiYuan has Arbitrary Document Reading within the Publishing Service (critical 9.8) - [CVE-2026-33670](https://insights.sbomify.com/CVE-2026-33670/): SiYuan has directory traversal within its publishing service (critical 9.8) - [CVE-2026-32767](https://insights.sbomify.com/CVE-2026-32767/): SiYuan: Authorization Bypass Allows Arbitrary SQL Execution via Search API (critical 9.8) - [CVE-2024-53504](https://insights.sbomify.com/CVE-2024-53504/): SQL injection in n/a (critical 9.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-34453 and fix it if it is affected. What it is: CVE-2026-34453 is a high-severity missing authorization vulnerability in B3log Siyuan, published on 31 Mar 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-34453 exists. Affected packages and fixed versions: - github.com/siyuan-note/siyuan/kernel (Go): affected all versions; no fix listed - github.com/siyuan-note/siyuan/kernel (Go): affected all versions; fixed in 3.6.2 - github.com/siyuan-note/siyuan/kernel (Go): affected all versions; fixed in 3.6.2 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-34453/ (Markdown: https://insights.sbomify.com/CVE-2026-34453/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-34453 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-34453 - OSV: https://osv.dev/vulnerability/CVE-2026-34453 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-34453/ Summaries are generated and may contain mistakes; the official description above is the record.