# CVE-2026-54069: SiYuan: Unauthenticated Admin API Access via Blanket chrome-extension:// Origin Allowlist

> Unauthenticated browser extensions can access admin APIs due to overly permissive origin allowlisting, enabling data theft and code execution.

- **Severity:** Critical 9.2 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/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:** Yes
- **Published:** 24 Jun 2026
- **Updated:** 25 Jun 2026
- **Also known as:** GHSA-hvr9-72v2-fff3, GO-2026-5961

## What is CVE-2026-54069?

CVE-2026-54069 is a critical authentication bypass 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, SiYuan Note's kernel HTTP server unconditionally trusts all chrome-extension:// origins, granting RoleAdministrator access to every installed browser extension without any authentication. Combined with the default empty AccessAuthCode on desktop installs, any Chrome/Chromium extension -- including a compromised legitimate extension via supply chain attack -- can make fully authenticated admin API calls to the SiYuan kernel at 127.0.0.1:6806, enabling data exfiltration, stored XSS injection, and configuration tampering. This vulnerability is fixed in 3.7.0.

Weakness: CWE-346 (Origin Validation Error)

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

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-54069?

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

## Is CVE-2026-54069 being exploited?

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

Public exploit code:

- SiYuan Note <= 3.6.5 - Authentication Bypass (nuclei): http/cves/2026/CVE-2026-54069.yaml

## Fix prompt for AI coding agents

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

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

## Sources

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

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