CVE
SiYuan information disclosure in publish getDoc API
SiYuan 3.6.0 before 3.8.9 with publish authentication disabled can expose body text of password-protected publish documents through the getDoc keywords field. Fixed in 3.8.9.
- Exploited
- No known exploitation
- Fix
- Fixed in 3.8.9
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 3.8.9.
Summary
SiYuan from 3.6.0 before 3.8.9 contains an information disclosure vulnerability that allows unauthenticated publish visitors to bypass per-document passwords via regex search in getDoc. Attackers can send POST requests to /api/filetree/getDoc with queryMethod 3 and a broad regex to read protected body text returned in the unfiltered keywords field.
Who should check
Teams running SiYuan 3.6.0 through 3.8.8 with the publish service and anonymous publish access, using per-document publish passwords to protect body text
“Affecting siyuan >= 3.6.0, < 3.8.9”
cve.now Index
- Exploitation0/40No signal
- Exposure20/25No login or user action needed, CISA rates it automatable · Unknown: Advisories don't say whether default setups are affected
- Reach10/20Affects npm packages
- Severity8.7/10CVSS 8.7
- No patch0/5No signal
What would change the score
- Would score about 84 if added to CISA KEV
- Would score about 79 if CISA's SSVC rates exploitation active
- Would score about 44 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 3.8.9.
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-126266 (SiYuan from 3.6.0 before 3.8.9 Publish-Password Bypass via getDoc Regex Keywords), 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-126266 (entry last updated 2026-11-13):
Affected:
- npm package SiYuan: from 3.6.0, fixed in 3.8.9
Fixed versions: 3.8.9.
Conditions (all must be true for the bug to be hit):
- Publish service with publish authentication disabled, so visitors get the anonymous Reader role (source: https://github.com/siyuan-note/siyuan/security/advisories/GHSA-qf37-w288-frvq)
- Target document is visible and protected by a per-document publish password (source: https://github.com/siyuan-note/siyuan/security/advisories/GHSA-qf37-w288-frvq)
- Attacker must know the visible password-protected document's ID or URL (source: https://github.com/siyuan-note/siyuan/security/advisories/GHSA-qf37-w288-frvq)
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-126266 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126266 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-qf37-w288-frvq
- https://www.vulncheck.com/advisories/siyuan-from-3.6.0-before-3.8.9-publish-password-bypass-via-getdoc-regex-keywords
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-126266
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-126266"}.Public exploit activity
- EPSS: 0.38%
Since disclosure: the repos PoC-in-GitHub lists and FIRST's daily EPSS score.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- SiYuannpm
From 3.6.0 · fixed in 3.8.9
Evidence 4
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · siyuan-note/siyuan · Advisory GHSA-qf37-w288-frvq |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-126266 |
| Record | NVD · CVE-2026-126266 |
| Other links 1 | |
| Link | vulncheck.com · advisories/siyuan-from-3.6.0-before-3.8.9-publish-password-bypass-via-getdoc-regex-keywords |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-126266
Is CVE-2026-126266 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?
The getDoc response places body text of protected publish documents in an unfiltered keywords field, so the per-document publish password does not keep that text from being read.Source: github.com, vulncheck.com
Which versions are affected by CVE-2026-126266?
SiYuan (npm): from 3.6.0 before 3.8.9.Source: cve.now feed data
Am I affected, and how do I check?
Affected are SiYuan versions from 3.6.0 before 3.8.9 where publish authentication is disabled, so visitors get the anonymous Reader role, and the document is visible and protected by a per-document publish password. To check, look at the SiYuan version in the app and the publish authentication setting of the publish service.Source: github.com, vulncheck.com
How do I fix CVE-2026-126266?
Upgrade to SiYuan 3.8.9, the fixed version named in the advisory.Source: github.com, vulncheck.com