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

CVE-2026-44586

HIGH · 8.3 CVSS v3.1 Published 2026-05-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges

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. From 2.1.12 to before 3.7.0. SiYuan's Bazaar marketplace renders package author metadata from the public bazaar stage feed into HTML without escaping. In the desktop app this becomes stored XSS, and because SiYuan's Electron windows are created with nodeIntegration: true and contextIsolation: false, a successful payload can call Node.js APIs and execute code on the host. 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's Bazaar marketplace renders package author metadata from the public bazaar feed into HTML without escaping, creating stored XSS. In the Electron desktop app, this XSS becomes exploitable for remote code execution because windows are created with nodeIntegration: true and contextIsolation: false, allowing attackers to call Node.js APIs directly from the rendered HTML.

MitigationUpgrade to SiYuan version 3.7.0 or later. If immediate upgrade is not possible, disable or restrict access to the Bazaar marketplace feature until the upgrade can be applied.

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
High
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/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 if SiYuan is installed
    Check for SiYuan application installation - look for SiYuan executable or app in standard installation locations (e.g., Program Files on Windows, Applications folder on macOS)
    Affected if SiYuan desktop application is present on the system
  2. Check installed SiYuan version
    Open SiYuan, then go to Help > About, or check the application metadata/file version to determine the exact version number
    Affected if Version is earlier than 3.7.0 (e.g., 3.6.x, 3.5.x, etc.)
  3. Determine if Bazaar marketplace has been accessed
    Look for Bazaar-related data, logs, or cached marketplace content in the SiYuan user data directory (typically in the workspace folder under .siyuan or similar)
    Affected if User has accessed or synced with the Bazaar marketplace feature
  4. Verify Electron security context (optional context for RCE severity)
    If possible, inspect the Electron configuration files or main process code bundled with the application for nodeIntegration and contextIsolation settings
    Affected if nodeIntegration is true AND contextIsolation is false (this configuration enables the RCE path from XSS)

User is affected if SiYuan desktop app version is earlier than 3.7.0 and the Bazaar marketplace feature has been accessed, with the Electron security misconfiguration present enabling the full RCE exploit chain.

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 version 3.7.0 or later. If immediate upgrade is not possible, disable or restrict access to the Bazaar marketplace feature until the upgrade can be applied.

Recommended fix High confidence

3.7.0

  1. 1. Back up your SiYuan data directory and any workspace configurations
  2. 2. Download SiYuan version 3.7.0 or later from the official GitHub releases (github.com/siyuan-note/siyuan/releases)
  3. 3. Close the currently running SiYuan application completely
  4. 4. Install version 3.7.0 by replacing the existing installation
  5. 5. Launch SiYuan and verify the application functions normally
  6. 6. Test the Bazaar marketplace functionality to confirm the fix is applied
Caveat Major version jump from 2.x to 3.x may include breaking changes; review release notes before upgrading

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-44586 — 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-44586 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