# CVE-2026-54068: SiYuan: Unauthenticated SQLite Data Exfiltration via Template Injection in /api/icon/getDynamicIcon

> Unauthenticated attackers can exfiltrate all user notes and data from SiYuan via SQL injection in an unprotected API endpoint.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/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:** 24 Jun 2026
- **Updated:** 25 Jun 2026
- **Also known as:** GHSA-gcm7-57gf-953c, GO-2026-5958

## What is CVE-2026-54068?

CVE-2026-54068 is a medium-severity missing authorization vulnerability in siyuan-note siyuan, published on 24 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SiYuan is an open-source personal knowledge management system. Prior to 3.7.0, the /api/icon/getDynamicIcon endpoint is explicitly excluded from authentication in SiYuan's kernel router (router.go, "不需要鉴权" -- no auth needed). When called with type=8 and a valid block id parameter, this endpoint invokes RenderDynamicIconContentTemplate, which executes a Go template that includes the querySQL and queryBlocks functions. These functions run arbitrary SELECT statements against the SiYuan SQLite database. An unauthenticated network-adjacent attacker who knows a valid block ID can exfiltrate all user note content, tags, asset references, and block attributes from the database. This vulnerability is fixed in 3.7.0.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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

3 open source packages ship an affected version, including github.com/siyuan-note/siyuan/kernel.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/siyuan-note/siyuan/kernel` | Go | All versions | 0.0.0-20260628153353-2d5d72223df4 |
| `github.com/siyuan-note/siyuan/kernel` | Go | All versions | 0.0.0-20260628153353-2d5d72223df4 |
| `github.com/siyuan-note/siyuan/kernel` | Go | All versions | 0.0.0-20260628153353-2d5d72223df4 |

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

Upgrade github.com/siyuan-note/siyuan/kernel to 0.0.0-20260628153353-2d5d72223df4 or later.

## Is CVE-2026-54068 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-54068 is a medium-severity missing authorization vulnerability in siyuan-note siyuan, published on 24 Jun 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-54068 exists.

Affected packages and fixed versions:
- github.com/siyuan-note/siyuan/kernel (Go): affected all versions; fixed in 0.0.0-20260628153353-2d5d72223df4
- github.com/siyuan-note/siyuan/kernel (Go): affected all versions; fixed in 0.0.0-20260628153353-2d5d72223df4
- github.com/siyuan-note/siyuan/kernel (Go): affected all versions; fixed in 0.0.0-20260628153353-2d5d72223df4

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-54068/ (Markdown: https://insights.sbomify.com/CVE-2026-54068/index.md)
```

## Sources

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

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