SiYuan before v3.6.1 fails to sanitize package metadata and README content in the Bazaar marketplace, allowing malicious package authors to inject arbitrary HTML and JavaScript. Attackers can achieve remote code execution on any user browsing the Bazaar by embedding XSS payloads in package displayName, description, or README fields, exploiting Electron's nodeIntegration setting to execute OS commands.
This CVE has been withdrawn by MITRE
MITRE marked CVE-2026-56395 as REJECTED on . It is no longer considered a valid vulnerability record. The original content below is preserved for historical reference only.
Reason given by MITRE
This record is a duplicate; use CVE-2026-56397 instead.
CVE-2026-56395
✕ Withdrawn — historical dataCRITICALPre-NVD 9.6
9.6CVSS
- CVSS v3
- 9.6
- EchelonGraph score
- Not yet assessedThis CVE record was withdrawn by its numbering authority, so there is no vulnerability to rate.
- EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- —Not applicable: this CVE ID was withdrawn
Published
June 21, 2026
Last Modified
June 22, 2026
References (2)
- disclosure@vulncheck · CISA-ADPhttps://github.com/siyuan-note/siyuan/security/advisories/GHSA-v3mg-9v85-fcm7
- disclosure@vulncheckhttps://www.vulncheck.com/advisories/siyuan-remote-code-execution-via-malicious-bazaar-package-metadata-and-readme
Frequently asked(4)
What is CVE-2026-56395?
CVE-2026-56395 is a rejected CVE ID: its record was withdrawn on September 17, 2026 and no longer describes a vulnerability. Reason given: This record is a duplicate; use CVE-2026-56397 instead. Its record names CVE-2026-56397 as the replacement.
When was the CVE record for CVE-2026-56395 published?
The CVE record for CVE-2026-56395 was published on June 21, 2026. EchelonGraph's copy of the record carries a last-modified date of June 22, 2026; the record at its source may have been updated since.
What is the CVSS score of CVE-2026-56395?
CVE-2026-56395 has a CVSS base score of 9.6 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-56395?
There is nothing to remediate under CVE-2026-56395: it is a rejected (withdrawn) CVE ID and no longer describes a vulnerability. Its record names CVE-2026-56397 as the replacement; act on that CVE instead.