dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-55570

CRITICAL · 9.0 CVSS v3.1 Published 2026-06-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 8 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
SiYuan is an open-source personal knowledge management system. Prior to 3.7.0, it does not escape the untrusted fields (name, version, author, description) when they are serialized into the data-obj HTML attribute of each marketplace card. Because the attribute is single-quoted and the value is produced with JSON.stringify() (which does not escape ', <, or >), a package whose name contains a single quote breaks out of the attribute and injects arbitrary HTML. In the desktop client the main BrowserWindow runs with nodeIntegration: true, contextIsolation: false, so the injected markup escalates from DOM XSS to arbitrary OS command execution. This is the same root cause and same impact as the original advisory, reached through a sibling sink the patch did not cover. This vulnerability is fixed in 3.7.0.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

SiYuan prior to 3.7.0 fails to escape untrusted package metadata (name, version, author, description) when serializing into single-quoted HTML data-obj attributes. JSON.stringify() does not escape single quotes, allowing packages with quotes in their name to break out of the attribute and inject arbitrary HTML. In the desktop Electron client with nodeIntegration:true and contextIsolation:false, this DOM XSS escalates to arbitrary OS command execution.

MitigationUpgrade to SiYuan 3.7.0 or later. If immediate upgrade is not feasible, restrict package installation sources and disable the desktop client until patched.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify SiYuan version
    Locate the installed SiYuan version (typically via Help > About, a version file, or the application's main window). Compare it against the affected range: any version prior to 3.7.0 is vulnerable.
    Affected if Installed version is prior to 3.7.0
  2. Confirm marketplace feature is in use
    Verify that the SiYuan marketplace or package installation feature is accessible or has been used. The vulnerable code path triggers when marketplace cards are serialized into HTML.
    Affected if Marketplace functionality is available or has been used to install packages
  3. Identify if running desktop client
    Determine if running the Electron-based desktop client (as opposed to browser-based or self-hosted web version). Check for the presence of SiYuan desktop executable and Electron runtime indicators.
    Affected if Running the SiYuan desktop client application
  4. Check Electron security configuration (for RCE escalation)
    For desktop clients, inspect the Electron configuration or webPreferences settings. Look for nodeIntegration:true and contextIsolation:false settings in the application configuration or main process files.
    Affected if Desktop client has nodeIntegration enabled AND contextIsolation disabled (allows XSS to escalate to OS command execution)

User is affected if running SiYuan version prior to 3.7.0 with marketplace feature accessible, especially desktop client with nodeIntegration:true and contextIsolation:false.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to SiYuan 3.7.0 or later. If immediate upgrade is not feasible, restrict package installation sources and disable the desktop client until patched.

Recommended fix High confidence

3.7.0

  1. Upgrade SiYuan to version 3.7.0 or later to remediate this vulnerability.

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA3.0 h
20.0 hours of engineering $3,420
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,472.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-55570 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-55570 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data