CVE
SiYuan remote code execution via XSS in attribute view images
Affects SiYuan through v3.8.9 when a database (Attribute View) has an Assets field, with the attribute panel shown by default. CVSS scores it 9.4 critical. Fixed in 3.8.10.
- Exploited
- No known exploitation
- Fix
- Fixed in 3.8.10
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. SiYuan versions through v3.8.9 are affected A database (Attribute View) with an Assets field Database attribute panel shown on documents, on by default
Summary
SiYuan before 3.8.10 contains a stored cross-site scripting vulnerability in genAVValueHTML() that allows attackers who can store Attribute View asset values to inject script through an unescaped image src attribute. Attackers can store an image URL containing a double quote and onerror handler that executes OS commands via Node.js in the desktop app when victims open the bound note or row attribute panel.
Who should check
Teams running SiYuan v3.8.9 and earlier, as desktop app or self-hosted Docker, with Attribute View Assets fields in their notes
Not fixed by: Earlier fixes for the aria-label and table-cell paths do not cover this image src.
“Affected: every release through the latest, v3.8.9”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.4/10CVSS 9.4
- No patch0/5No signal
What would change the score
- Would score about 67 if added to CISA KEV
- Would score about 62 if CISA's SSVC rates exploitation active
- Would score about 24 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
SiYuan versions through v3.8.9 are affected A database (Attribute View) with an Assets field Database attribute panel shown on documents, on by defaultUpgrade 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-130679 (SiYuan before 3.8.10 Stored XSS to RCE via Attribute View Asset Image src), 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-130679 (entry last updated 2026-11-18):
Affected:
- siyuan-note siyuan: fixed in 3.8.10
Fixed versions: 3.8.10.
Conditions (all must be true for the bug to be hit):
- SiYuan versions through v3.8.9 are affected (source: https://github.com/siyuan-note/siyuan/security/advisories/GHSA-3qqh-fmrp-8vfq)
- A database (Attribute View) with an Assets field (source: https://github.com/siyuan-note/siyuan/security/advisories/GHSA-3qqh-fmrp-8vfq)
- Database attribute panel shown on documents, on by default (source: https://github.com/siyuan-note/siyuan/security/advisories/GHSA-3qqh-fmrp-8vfq)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, low-privilege login, a user action.
CISA KEV: CVE-2026-130679 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130679 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/siyuan-note/siyuan/security/advisories/GHSA-3qqh-fmrp-8vfq
- https://github.com/siyuan-note/siyuan/commit/3f4a2ca741411ebf0908ef1b7b86500a4ef4c20c
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-130679
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-130679"}.Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
Affected versions
- siyuan-note siyuan
fixed in 3.8.10
Evidence 4
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · siyuan-note/siyuan · Advisory GHSA-3qqh-fmrp-8vfq |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-130679 |
| Record | NVD · CVE-2026-130679 |
| Other links 1 | |
| Patch | GitHub · siyuan-note/siyuan · Commit 3f4a2ca7 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-130679
Is CVE-2026-130679 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 attacker can store JavaScript in an Assets field's image src, and it runs when a user opens the note or row attribute panel that the database is bound to. In the desktop app, this means operating system command execution as the user.Source: github.com
Which versions are affected by CVE-2026-130679?
siyuan: before 3.8.10.Source: cve.now feed data
Am I affected, and how do I check?
Every SiYuan release through v3.8.9 is affected. A stock installation with a database (Attribute View) that has an Assets field is in the affected setup, and the database attribute panel (databaseAttrShow) is on by default with no setting to change. To check, look at your SiYuan version and whether any database has an Assets field.Source: github.com
How do I fix CVE-2026-130679?
Upgrade to SiYuan 3.8.10 or later.Source: github.com