CVE-2026-56397

CRITICALPre-NVD 9.69.6—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.7% (51st percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this weekElevated
9.6EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 9.6Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
9.6
EG Score
9.6CRITICALmedium confidence
EG Risk
59
EG Risk 59/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity96% × 45%
Exploitation40% × 40%
Automatability0% × 15%
CISA SSVC: Track at low, Track* at medium and Attend at high mission impact.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
40th
KEV
Not listed

CISA SSVCTrack at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

June 21, 2026

Last Modified

October 8, 2026

Advisory Details (2)

Auto-updated Oct 7, 2026
🔬 Proof of concept available. Patch available. Sources: github.
githubMentions a patch (unverified)🟡 PoC Available

Remote Code Execution via Malicious Bazaar Package — Marketplace XSS · Advisory · siyuan-note/siyuan · GitHub

https://github.com/siyuan-note/siyuan/security/advisories/GHSA-v3mg-9v85-fcm7
generic

SiYuan - Remote Code Execution via Malicious Bazaar Package Metadata and README | Advisories | VulnCheck

https://www.vulncheck.com/advisories/siyuan-remote-code-execution-via-malicious-bazaar-package-metadata-and-readme-2

Vendor Advisories for CVE-2026-56397(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
gogithub.com/siyuan-note/siyuan/kernel—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(2 across 1 ecosystem)
Go(2)
PackageVulnerable rangeFix by version rangeDependents
github.com/siyuan-note/siyuan/kernel—
  • every version through 0.0.0-20260313024916-fd6526133bb3: no fix on record
  • every version up to 0.0.0-20260317012524-fe4523fff2c8: fixed in 0.0.0-20260317012524-fe4523fff2c8
—
siyuan—
  • every version through 0.0.0-20260313024916-fd6526133bb3: no fix on record
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 35× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 431 total refreshes for this CVE.

  1. 2026-10-10 20:00 UTCEPSS rescore
  2. 2026-10-09 20:07 UTCEPSS rescore
  3. 2026-10-08 17:13 UTCEPSS rescore
  4. 2026-10-08 16:40 UTCEG score recompute
  5. 2026-10-08 16:40 UTCGHSA enrichment
  6. 2026-10-08 15:46 UTCEG score recompute
  7. 2026-10-08 15:46 UTCGHSA enrichment
  8. 2026-10-07 23:48 UTCEPSS rescore
  9. 2026-10-06 15:18 UTCEPSS rescore
  10. 2026-10-05 17:43 UTCEPSS rescore
  11. 2026-10-04 23:22 UTCEPSS rescore
  12. 2026-10-03 14:49 UTCOSV refresh
  13. 2026-10-03 14:26 UTCEPSS rescore
  14. 2026-10-02 17:56 UTCEPSS rescore
  15. 2026-10-01 19:50 UTCEPSS rescore
  16. 2026-09-30 15:03 UTCEPSS rescore
  17. 2026-09-29 15:22 UTCEPSS rescore
  18. 2026-09-28 13:51 UTCEPSS rescore
  19. 2026-09-27 13:48 UTCEPSS rescore
  20. 2026-09-26 15:59 UTCEPSS rescore
  21. 2026-09-24 14:04 UTCEPSS rescore
  22. 2026-09-23 17:54 UTCEPSS rescore
  23. 2026-09-20 20:16 UTCEPSS rescore
  24. 2026-09-18 19:28 UTCEPSS rescore
  25. 2026-09-17 19:31 UTCEPSS rescore
Show 75 more
  1. 2026-09-16 14:08 UTCEPSS rescore
  2. 2026-09-16 05:15 UTCEPSS rescore
  3. 2026-09-15 03:11 UTCEPSS rescore
  4. 2026-09-14 06:29 UTCGHSA enrichment
  5. 2026-09-14 02:10 UTCEG score recompute
  6. 2026-09-14 02:10 UTCGHSA enrichment
  7. 2026-09-13 16:47 UTCEPSS rescore
  8. 2026-09-13 12:52 UTCEG score recompute
  9. 2026-09-13 12:52 UTCGHSA enrichment
  10. 2026-09-11 14:53 UTCEPSS rescore
  11. 2026-09-10 09:35 UTCEPSS rescore
  12. 2026-09-08 22:01 UTCEPSS rescore
  13. 2026-09-07 16:01 UTCEPSS rescore
  14. 2026-09-06 13:47 UTCEPSS rescore
  15. 2026-09-04 05:07 UTCEPSS rescore
  16. 2026-09-02 14:12 UTCEPSS rescore
  17. 2026-09-01 13:54 UTCEPSS rescore
  18. 2026-09-01 04:40 UTCEPSS rescore
  19. 2026-08-31 01:00 UTCGHSA enrichment
  20. 2026-08-30 20:41 UTCEG score recompute
  21. 2026-08-30 20:41 UTCGHSA enrichment
  22. 2026-08-30 19:17 UTCEPSS rescore
  23. 2026-08-30 01:22 UTCEPSS rescore
  24. 2026-08-28 21:42 UTCEPSS rescore
  25. 2026-08-27 14:25 UTCEPSS rescore
  26. 2026-08-26 14:46 UTCEPSS rescore
  27. 2026-08-25 13:49 UTCEPSS rescore
  28. 2026-08-25 06:56 UTCGHSA enrichment
  29. 2026-08-25 02:37 UTCGHSA enrichment
  30. 2026-08-24 22:15 UTCEG score recompute
  31. 2026-08-24 22:15 UTCGHSA enrichment
  32. 2026-08-24 13:57 UTCEG score recompute
  33. 2026-08-24 13:57 UTCGHSA enrichment
  34. 2026-08-24 06:49 UTCGHSA enrichment
  35. 2026-08-24 01:12 UTCGHSA enrichment
  36. 2026-08-23 20:53 UTCGHSA enrichment
  37. 2026-08-23 16:34 UTCGHSA enrichment
  38. 2026-08-23 12:15 UTCGHSA enrichment
  39. 2026-08-23 07:54 UTCGHSA enrichment
  40. 2026-08-23 03:32 UTCEG score recompute
  41. 2026-08-23 03:32 UTCGHSA enrichment
  42. 2026-08-23 00:19 UTCEPSS rescore
  43. 2026-08-22 22:54 UTCEG score recompute
  44. 2026-08-22 22:54 UTCGHSA enrichment
  45. 2026-08-21 23:49 UTCEPSS rescore
  46. 2026-08-21 23:21 UTCGHSA enrichment
  47. 2026-08-21 18:54 UTCGHSA enrichment
  48. 2026-08-21 14:35 UTCGHSA enrichment
  49. 2026-08-21 10:16 UTCGHSA enrichment
  50. 2026-08-21 05:56 UTCGHSA enrichment
  51. 2026-08-21 01:37 UTCEG score recompute
  52. 2026-08-21 01:37 UTCGHSA enrichment
  53. 2026-08-20 22:55 UTCEPSS rescore
  54. 2026-08-20 21:17 UTCGHSA enrichment
  55. 2026-08-20 16:58 UTCGHSA enrichment
  56. 2026-08-20 12:23 UTCGHSA enrichment
  57. 2026-08-20 07:53 UTCEG score recompute
  58. 2026-08-20 07:53 UTCGHSA enrichment
  59. 2026-08-19 17:04 UTCEPSS rescore
  60. 2026-08-19 15:37 UTCGHSA enrichment
  61. 2026-08-19 11:01 UTCGHSA enrichment
  62. 2026-08-19 05:47 UTCEG score recompute
  63. 2026-08-19 05:47 UTCGHSA enrichment
  64. 2026-08-18 13:48 UTCEPSS rescore
  65. 2026-08-17 14:51 UTCEG score recompute
  66. 2026-08-17 14:50 UTCGHSA enrichment
  67. 2026-08-17 13:47 UTCEPSS rescore
  68. 2026-08-17 10:31 UTCGHSA enrichment
  69. 2026-08-17 06:12 UTCGHSA enrichment
  70. 2026-08-17 00:50 UTCGHSA enrichment
  71. 2026-08-16 20:31 UTCGHSA enrichment
  72. 2026-08-16 16:11 UTCEG score recompute
  73. 2026-08-16 16:11 UTCGHSA enrichment
  74. 2026-08-16 14:56 UTCEPSS rescore
  75. 2026-08-16 11:51 UTCGHSA enrichment

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-56397?
CVE-2026-56397 is a critical vulnerability published on June 21, 2026. 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…
When was CVE-2026-56397 disclosed?
CVE-2026-56397 was first published on June 21, 2026, with the most recent update on October 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-56397 actively exploited?
CVE-2026-56397 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (40th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-56397?
CVE-2026-56397 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-56397?
A fix for CVE-2026-56397 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-56397 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-56397

Explore →

Is Your Infrastructure Affected by CVE-2026-56397?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs