Skip to main content
Menu
CVEs

SiYuan authorization bypass leaks asset text in asset API

Affects SiYuan 3.8.0 before 3.8.10 when a publicly accessible host document contains an attribute view whose rows come from documents with publishing disabled. Fixed in SiYuan 3.8.10.

CVE-2026-134247Published November 21, 2026, updated

8.7HighCNA
Exploited
No known exploitation
Fix
Fixed in 3.8.10
Who is exposed
Not reported

Summary

SiYuan, a note-taking application, has an incorrect authorization flaw in versions before 3.8.10 that lets anyone on the network, without logging in, read the full indexed text of confidential files. The attacker first gets the file path from a publicly shared document, then uses it to pull the file's contents.

Written by a model

Original description

SiYuan 3.8.0 before 3.8.10 contains an incorrect authorization vulnerability that allows anonymous attackers to read indexed asset text referenced only by publish-disabled attribute-view rows. Attackers can request /api/asset/getDocAssets on a public host document to obtain the leaked asset path, then query /api/search/getAssetContentByPath to retrieve the confidential file's full indexed text.

Who should check

Teams running SiYuan 3.8.0 through 3.8.9 with the publish service hosting public documents that contain attribute views with asset values.

“SiYuan 3.8.0 before 3.8.10 contains an incorrect authorization vulnerability”

vulncheck.com

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-134247 (SiYuan 3.8.0 before 3.8.10 Incorrect Authorization Exposes Asset Text via getAssetContentByPath), 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-134247 (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):
- SiYuan 3.8.0 before 3.8.10 (affecting siyuan >= 3.8.0, < 3.8.10). (source: https://www.vulncheck.com/advisories/siyuan-3.8.0-before-3.8.10-incorrect-authorization-exposes-asset-text-via-getassetcontentbypath)
- A publicly accessible host document contains an attribute view with an MAsset value bound to a row whose source document has publishing disabled, and an indexed text asset referenced by that value. (source: https://github.com/siyuan-note/siyuan/security/advisories/GHSA-q2x4-crw5-q567)
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-134247 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134247 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-q2x4-crw5-q567
- https://github.com/siyuan-note/siyuan/commit/9a087492f1d3aeb97c22db156ed27769ebc87ac8
- https://www.vulncheck.com/advisories/siyuan-3.8.0-before-3.8.10-incorrect-authorization-exposes-asset-text-via-getassetcontentbypath
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-134247
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-134247"}.

Affected versions

cve.now Index

36Pof 100 · provisional · methodology v3
  • 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

  1. CVE published
  2. First seen by cve.now

Evidence 5

Questions about CVE-2026-134247

Is CVE-2026-134247 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?

An anonymous remote attacker can read the full indexed text of private assets that are referenced only by publish-disabled attribute-view rows. The result is loss of confidentiality, such as disclosure of confidential document attachments or other indexed files.

Source: vulncheck.com, github.com

Which versions are affected by CVE-2026-134247?

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 SiYuan 3.8.0 up to but not including 3.8.10 are affected. The vulnerable setup needs a publicly accessible host document containing an attribute view with an MAsset value bound to a row whose source document has publishing disabled, plus an indexed text asset referenced by that value. To check, compare the installed SiYuan version against the affected range and review whether such attribute views exist in publicly published documents.

Source: vulncheck.com, github.com

How do I fix CVE-2026-134247?

Upgrade SiYuan to version 3.8.10 or later, which is the fixed version named for this vulnerability.

Source: vulncheck.com, github.com

No corrections so far. Something wrong on this page? Report an error.