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.
- Exploited
- No known exploitation
- Fix
- Fixed in 3.8.10
- Who is exposed
- Not reported
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
Original 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.
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.
“Affecting siyuan >= 3.8.0, < 3.8.10”
What to do
Upgrade to a fixed version: 3.8.10.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
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"}.Affected versions
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach10/20Affects Go packages
- Severity8.7/10CVSS 8.7
- No patch0/5No signal
What would change the score
- Would score about 81 if added to CISA KEV
- Would score about 76 if CISA's SSVC rates exploitation active
- Would score about 41 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
Evidence 5
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · siyuan-note/siyuan · Advisory GHSA-xxqp-6jxw-qr84 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-134245 |
| Record | NVD · CVE-2026-134245 |
| Other links 2 | |
| Patch | GitHub · siyuan-note/siyuan · Commit 76bbb54d |
| Link | vulncheck.com · advisories/siyuan-3.8.0-before-3.8.10-incorrect-authorization-via-assets-cross-document-asset-collision |
Questions about CVE-2026-134245
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: cve.now feed data
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: github.com, vulncheck.com
Which versions are affected by CVE-2026-134245?
github.com/siyuan-note/siyuan/kernel (Go): from 3.8.0 before 3.8.10.
Source: cve.now feed data
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: github.com, vulncheck.com
How do I fix CVE-2026-134245?
Upgrade SiYuan to version 3.8.10 or later, which is the fixed version.
Source: github.com, vulncheck.com
Related
- CVE-2026-72811SiYuan before v3.7.4 SQL Injection via backlink search
- CVE-2026-126265SiYuan 2.1.0 before 3.8.9 CAPTCHA Bypass via Stale Login Cookie
- CVE-2026-134247SiYuan 3.8.0 before 3.8.10 Incorrect Authorization Exposes Asset Text via getAssetContentByPath
- CVE-2026-85175SiYuan before v3.8.2 TLS Private Key Disclosure via getFile
- CVE-2026-74904SiYuan before v3.7.4 Missing Authorization via block API
- CVE-2026-73054SiYuan before v3.7.4 Authentication Bypass via WebSocket
No corrections so far. Something wrong on this page? Report an error.