siyuan-note/siyuan information disclosure in Markdown export block references
Affects SiYuan 3.6.0 before 3.8.10 when a public document stores a block reference to a hidden, disabled, or password-protected document and is exported to Markdown. Fixed in 3.8.10.
- Exploited
- No known exploitation
- Fix
- Fixed in 3.8.10
- Who is exposed
- Specific setups only
Summary
SiYuan has an information disclosure flaw that lets an authenticated Reader remotely read the body text of hidden, disabled, or password-protected documents without the publish password. The attacker requests the Markdown export (copyStdMarkdown) for a public document that references the protected one, and the block-reference footnote resolution exposes its contents.
Written by a model
Original description
SiYuan 3.6.0 before 3.8.10 contains an information disclosure vulnerability that allows authenticated Readers to read protected documents through block-reference footnote resolution in Markdown export. Attackers can request copyStdMarkdown for a public document referencing a hidden, disabled, or password-protected document to disclose its body text without the publish password.
Who should check
Teams running SiYuan before 3.8.10 (from 3.6.0) with the publish service, where authenticated Reader accounts can access public documents.
“Affecting siyuan >= 3.6.0, < 3.8.10”
What to do
Check whether your setup matches what the bug needs.
SiYuan version 3.6.0 up to, but not including, 3.8.10. The public document being exported contains a stored block reference to a target in a hidden, disabled, or password-protected document. Markdown export uses block-reference footnote resolution, which the default export configuration enables.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-134248 (SiYuan 3.6.0 before 3.8.10 Information Disclosure via copyStdMarkdown Block References), 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-134248 (entry last updated 2026-11-21):
Affected:
- npm package siyuan-note/siyuan: from 3.6.0, fixed in 3.8.10
Fixed versions: 3.8.10.
Conditions (all must be true for the bug to be hit):
- SiYuan version 3.6.0 up to, but not including, 3.8.10. (source: https://www.vulncheck.com/advisories/siyuan-3.6.0-before-3.8.10-information-disclosure-via-copystdmarkdown-block-references)
- The public document being exported contains a stored block reference to a target in a hidden, disabled, or password-protected document. (source: https://github.com/siyuan-note/siyuan/security/advisories/GHSA-qwg4-fj37-jjqq)
- Markdown export uses block-reference footnote resolution, which the default export configuration enables. (source: https://github.com/siyuan-note/siyuan/security/advisories/GHSA-qwg4-fj37-jjqq)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-134248 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134248 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Packages (npm): 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-qwg4-fj37-jjqq
- https://github.com/siyuan-note/siyuan/commit/7b70b90a5ec49b13f81b5f2779f57a7fdf53dd57
- https://www.vulncheck.com/advisories/siyuan-3.6.0-before-3.8.10-information-disclosure-via-copystdmarkdown-block-references
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-134248
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-134248"}.Affected versions
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach10/20Affects npm packages
- Severity8.3/10CVSS 8.3
- No patch0/5No signal
What would change the score
- Would score about 76 if added to CISA KEV
- Would score about 71 if CISA's SSVC rates exploitation active
- Would score about 33 if CISA's SSVC rates it automatable
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-qwg4-fj37-jjqq |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-134248 |
| Record | NVD · CVE-2026-134248 |
| Other links 2 | |
| Patch | GitHub · siyuan-note/siyuan · Commit 7b70b90a |
| Link | vulncheck.com · advisories/siyuan-3.6.0-before-3.8.10-information-disclosure-via-copystdmarkdown-block-references |
Questions about CVE-2026-134248
Is CVE-2026-134248 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 authenticated Reader can read the body text of hidden, disabled, or password-protected documents without the publish password. This works by having a public document reference the protected document.
Source: vulncheck.com, github.com
Which versions are affected by CVE-2026-134248?
siyuan-note/siyuan (npm): from 3.6.0 before 3.8.10.
Source: cve.now feed data
Am I affected, and how do I check?
SiYuan 3.6.0 up to, but not including, 3.8.10 is affected. The setup also needs a public document that holds a stored block reference to a target in a hidden, disabled, or publish-password-protected document, and Markdown export that uses block-reference footnote resolution, which the default export configuration (BlockRefMode 4) enables. To check, look at the installed SiYuan version and at the export block-reference setting.
Source: vulncheck.com, github.com
How do I fix CVE-2026-134248?
Upgrade SiYuan to 3.8.10 or later.
Source: vulncheck.com, github.com
Related
- CVE-2026-130682SiYuan before 3.8.10 Stored XSS to RCE via Table Caption
- CVE-2026-130681SiYuan before 3.8.10 Stored XSS to RCE via Attribute View Name
- CVE-2026-130680SiYuan 3.3.0 before 3.8.10 Stored XSS to RCE via AttributeView Checkbox Column
- CVE-2026-130678SiYuan before 3.8.10 Stored XSS to RCE via Attribute View Column Name
- CVE-2026-130679SiYuan before 3.8.10 Stored XSS to RCE via Attribute View Asset Image src
- CVE-2026-130683SiYuan before 3.8.10 Path Traversal via /api/file/copyFile Deny-List Bypass
No corrections so far. Something wrong on this page? Report an error.