SiYuan before v3.8.1 Stored XSS via block name

Answer in brief

CVE-2026-82654 records a Unknown severity vulnerability in SiYuan before v3.8.1 Stored XSS via block name. The current sources do not mark it as known exploited. The current feed maps siyuan-note/siyuan (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Aug 30, 2026Updated Aug 30, 2026Source checked Aug 30, 2026First seen by HOL Aug 30, 2026Material review Aug 30, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps siyuan-note/siyuan (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
siyuan-note/siyuangeneric	>=0 <3.8.1	3.8.1

Recommended response

Check inventory. Check lockfiles and deployed manifests for siyuan-note/siyuan.
Review the reported fix. Update siyuan-note/siyuan to 3.8.1 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Aug 30, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Aug 30, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Aug 30, 2026

Sources and claim methodology

Upstream source description

SiYuan before v3.8.1 fails to properly escape block name, alias, and memo fields in hint, backlink, and breadcrumb rendering functions. Attackers can set a block's name to contain HTML/script tags that execute when another user views documents referencing or displaying that block.

Quoted source text, attributed separately from HOL analysis.