NVD / CVE Program· CNA GitHub_M

CVE-2026-32938: SiYuan has an Arbitrary File Read in its Desktop Publish Service

Noroxi assessment

Priority: Monitor (action score 26/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.43% (FIRST EPSS).
Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
Fixed version: siyuan-note siyuan 3.6.1.
Severity is disputed: the assigning authority (CNA) scores it 9.9, NVD 6.5.

Low priority for now. Upgrade to siyuan-note siyuan 3.6.1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

SiYuan is a personal knowledge management system. In versions 3.6.0 and below, the /api/lute/html2BlockDOM on the desktop copies local files pointed to by file:// links in pasted HTML into the workspace assets directory without validating paths against a sensitive-path list. Together with GET /assets/*path, which only requires authentication, a publish-service visitor can cause the desktop kernel to copy any readable sensitive file and then read it via GET, leading to exfiltration of sensitive files. This issue has been fixed in version 3.6.1.

MediumCVSS 6.5 · v3.1—No exploit Fix available

Path traversal

Published: Mar 20, 2026
Updated: Jun 17, 2026
EPSS: 0.4% · 37th percentile
CWE: CWE-22

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 26 / 40 · 6.5 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.4%

CISA SSVC decision

Exploitation: proof of concept
Automatable: no
Technical impact: total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: 6.5
CNA · GitHub_M: 9.9; 3.4 point gap

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:H

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
b3log	siyuan	cpe:2.3:a:b3log:siyuan

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

b3log siyuanbefore 3.6.1

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

siyuan-note siyuan
- < 3.6.1affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Go	github.com/siyuan-note/siyuan/kernel	from 0	—
Go	github.com/siyuan-note/siyuan/kernel	up to and including 0.0.0-20260313024916-fd6526133bb3	—

Same product

b3log: all records

Other highest-scoring records for the same primary product.

CVE-2026-32767SiYuan: Authorization Bypass Allows Arbitrary SQL Execution via Search API
39Monitor
CVE-2026-30869SiYuan has a Path Traversal in /export Endpoint Allows Arbitrary File Read and Secret Leakage
39Monitor
CVE-2024-53507A SQL injection vulnerability was discovered in Siyuan 3.1.11 in /getHistoryItems.
39Monitor

Published before and after this one in the same product

← EarlierCVE-2026-32751Mar 19, 2026 · SiYuan Vulnerable to Remote Code Execution via Stored XSS in Notebook Name - Mobile Interface
20Monitor
← EarlierCVE-2026-32815Mar 19, 2026 · SiYuan: Cross-Origin WebSocket Hijacking via Authentication Bypass — Unauthenticated Information Disclosure
21Monitor
Later →CVE-2026-32940Mar 20, 2026 · SiYuan has a SanitizeSVG bypass via data:text/xml in getDynamicIcon (incomplete fix for CVE-2026-29183)
24Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
siyuan-note siyuan	3.6.1 · description	Vendor (CNA)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

siyuan-note/siyuancommit 294b8b4

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

CVE-2026-3086910 days apartSiYuan has a Path Traversal in /export Endpoint Allows Arbitrary File Read and Secret Leakage
39Monitor
CVE-2026-327491 days apartSiYuan importSY/importZipMd: Path Traversal via multipart filename enables arbitrary file write
36Monitor
CVE-2025-67488101 days apartSiYuan: ZipSlip -> Arbitrary File Overwrite -> RCE
35Monitor
CVE-2024-55657464 days apartSiYuan has an arbitrary file read via /api/template/render
34Monitor
CVE-2024-55658464 days apartSiYuan has an arbitrary file read and path traversal via /api/export/exportResources
34Monitor
CVE-2024-55659464 days apartSiYuan has an arbitrary file write in the host via /api/asset/upload
34Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
A low-privileged account is enough.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: none
Availability: none

Attack vector: Network
Attack complexity: Low
Privileges required: Low
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: None
Availability impact: None

Weakness class (CWE)

CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

nvd-primary

Root cause

A user-supplied file name is joined with the allowed directory, but the result is never checked to confirm it is still inside that directory.

The bug in code

The whole CWE-22 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1const file = path.join(ROOT, req.query.name);
2res.sendFile(file);

Fixed

1const file = path.resolve(ROOT, req.query.name);
2if (!file.startsWith(ROOT + path.sep)) {
3  return res.sendStatus(400);
4}
5res.sendFile(file);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

—

Change log

Fix✗ → ✓Sep 29, 2026, 11:55 AM UTC

For records you follow, these changes also arrive as notifications. →

References

github.com/siyuan-note/siyuan/commit/294b8b429dea152cd1df522cddf406054c1619ad

Show all references (1 more)

github.com/siyuan-note/siyuan/releases/tag/v3.6.1

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records