SiYuan missing authorization in getDOMText exposes cached OCR text
Affects SiYuan 3.6.0 before 3.6.2 and 3.7.3 before 3.8.10 when publish authentication is disabled. Fixed in 3.6.2 and 3.8.10.
- Exploited
- No known exploitation
- Fix
- Fixed in 3.6.2, 3.8.10
- Who is exposed
- Not reported
Summary
SiYuan has a missing authorization flaw in its getDOMText endpoint. When publish authentication is disabled, a remote anonymous user can submit crafted DOM that references a known unpublished, non-encrypted asset path and read that asset's already-cached OCR text, without logging in.
Written by a model
Original description
SiYuan 3.6.0 before 3.6.2 and 3.7.3 before 3.8.10 contains a missing authorization vulnerability in the /api/block/getDOMText endpoint, which renders caller-supplied DOM without checking publish access for referenced image paths. When publish authentication is disabled, anonymous visitors can submit DOM referencing a known unpublished, non-encrypted asset path to retrieve its already-cached OCR text.
Who should check
Teams running SiYuan 3.6.x before 3.6.2 or 3.7.3 through 3.8.9 with a publish service where publish authentication is disabled.
“SiYuan 3.6.0 before 3.6.2 and 3.7.3 before 3.8.10”
What to do
Upgrade to a fixed version: 3.6.2, 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-134246 (SiYuan 3.6.0 before 3.6.2 and 3.7.3 before 3.8.10 Missing Authorization in getDOMText Exposes Cached OCR Text), 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-134246 (entry last updated 2026-11-21):
Affected:
- npm package SiYuan: from 3.6.0, fixed in 3.6.2
- npm package SiYuan: from 3.7.3, fixed in 3.8.10
Fixed versions: 3.6.2, 3.8.10.
Conditions (all must be true for the bug to be hit):
- Publish authentication is disabled. (source: https://www.vulncheck.com/advisories/siyuan-3.6.0-before-3.6.2-and-3.7.3-before-3.8.10-missing-authorization-in-getdomtext-exposes-cached-ocr-text)
- The target asset is known and not encrypted, and its OCR text is already cached. (source: https://github.com/siyuan-note/siyuan/security/advisories/GHSA-vmvr-gf8m-x483)
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-134246 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134246 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-vmvr-gf8m-x483
- https://github.com/siyuan-note/siyuan/commit/0432ef213d112e5ace886963f8e57fdf348c76c5
- https://www.vulncheck.com/advisories/siyuan-3.6.0-before-3.6.2-and-3.7.3-before-3.8.10-missing-authorization-in-getdomtext-exposes-cached-ocr-text
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-134246
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-134246"}.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 npm 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-vmvr-gf8m-x483 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-134246 |
| Record | NVD · CVE-2026-134246 |
| Other links 2 | |
| Patch | GitHub · siyuan-note/siyuan · Commit 0432ef21 |
| Link | vulncheck.com · advisories/siyuan-3.6.0-before-3.6.2-and-3.7.3-before-3.8.10-missing-authorization-in-getdomtext-exposes-cached-ocr-text |
Questions about CVE-2026-134246
Is CVE-2026-134246 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 flaw in the getDOMText function lacks an authorization check, so an anonymous visitor to a public SiYuan Reader can retrieve the full cached OCR text of a known, non-encrypted asset that is outside the published document and asset set.
Source: vulncheck.com, github.com
Which versions are affected by CVE-2026-134246?
SiYuan (npm): from 3.6.0 before 3.6.2. SiYuan (npm): from 3.7.3 before 3.8.10.
Source: cve.now feed data
Am I affected, and how do I check?
Versions 3.6.0 before 3.6.2 and 3.7.3 before 3.8.10 are in range, but the issue only applies when publish authentication is disabled and the asset's OCR text is already cached. To check, look at the SiYuan version shown in the app's settings and whether publish authentication is turned on in the publishing settings.
Source: vulncheck.com, github.com
How do I fix CVE-2026-134246?
Upgrade to SiYuan 3.6.2 or 3.8.10, depending on which release line you are on. The facts do not name any patch identifiers or a workaround.
Source: vulncheck.com, github.com
Related
- CVE-2026-130680SiYuan 3.3.0 before 3.8.10 Stored XSS to RCE via AttributeView Checkbox Column
- CVE-2026-126266SiYuan from 3.6.0 before 3.8.9 Publish-Password Bypass via getDoc Regex Keywords
- CVE-2026-134244SiYuan 3.8.0 before 3.8.10 LAN Sync Metadata Disclosure Before Peer Authentication
- 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-130678SiYuan before 3.8.10 Stored XSS to RCE via Attribute View Column Name
No corrections so far. Something wrong on this page? Report an error.