# CVE-2026-32767: SiYuan: Authorization Bypass Allows Arbitrary SQL Execution via Search API > Authenticated users can execute arbitrary SQL commands via the search API due to missing authorization checks, allowing data modification or deletion. - **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 20 Mar 2026 - **Updated:** 20 Mar 2026 - **Also known as:** CLEANSTART-2026-MD29809, GHSA-j7wh-x834-p3r7, GO-2026-4716 ## What is CVE-2026-32767? CVE-2026-32767 is a critical SQL injection vulnerability in B3log Siyuan, published on 20 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. Versions 3.6.0 and below contain an authorization bypass vulnerability in the /api/search/fullTextSearchBlock endpoint. When the method parameter is set to 2, the endpoint passes user-supplied input directly as a raw SQL statement to the underlying SQLite database without any authorization or read-only checks. This allows any authenticated user — including those with the Reader role — to execute arbitrary SQL statements (SELECT, DELETE, UPDATE, DROP TABLE, etc.) against the application's database. This is inconsistent with the application's own security model: the dedicated SQL endpoint (/api/query/sql) correctly requires both CheckAdminRole and CheckReadonly middleware, but the search endpoint bypasses these controls entirely. This issue has been fixed in version 3.6.1. Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command), CWE-863 (Incorrect Authorization) ## Which versions are affected by CVE-2026-32767? 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 to 0.0.0-20260313024916-fd6526133bb3 | None | | `github.com/siyuan-note/siyuan/kernel` | Go | All versions to 0.0.0-20260313024916-fd6526133bb3 | None | Products: B3log Siyuan. ## How do I fix CVE-2026-32767? Upgrade to a fixed version. ## Is CVE-2026-32767 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-32767 exists. ## 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-2024-53504](https://insights.sbomify.com/CVE-2024-53504/): SQL injection in n/a (critical 9.8) - [CVE-2024-53505](https://insights.sbomify.com/CVE-2024-53505/): SQL injection in n/a (critical 9.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-32767 and fix it if it is affected. What it is: CVE-2026-32767 is a critical SQL injection vulnerability in B3log Siyuan, published on 20 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-32767 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 up to 0.0.0-20260313024916-fd6526133bb3; no fix listed - github.com/siyuan-note/siyuan/kernel (Go): affected all versions up to 0.0.0-20260313024916-fd6526133bb3; no fix listed 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-32767/ (Markdown: https://insights.sbomify.com/CVE-2026-32767/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-32767 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-32767 - OSV: https://osv.dev/vulnerability/CVE-2026-32767 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-32767/ Summaries are generated and may contain mistakes; the official description above is the record.