CVE-2026-55570

CRITICALPre-NVD 9.09.0—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 75% of all CVEs by exploit prediction. 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
9.0
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 9.0Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
9.0
EG Score
9.0(medium)
EPSS
24.7%
KEV
Not listed

Published

June 24, 2026

Last Modified

June 25, 2026

Advisory Details (1)

Auto-updated Jun 25, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

Stored XSS results to Electron RCE in SiYuan marketplace via unescaped `data-obj` attribute (incomplete fix for GHSA-27qc-m5gf-jv5r) / Bypass for CVE-2026-45375's patch · Advisory · siyuan-note/siyuan · GitHub

https://github.com/siyuan-note/siyuan/security/advisories/GHSA-x88j-wgpr-h22x

Weakness Classification(3)

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

Data Freshness Timeline

(refreshed 56× in last 7d / 134× 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 134 total refreshes for this CVE.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-55570?
CVE-2026-55570 is a critical vulnerability published on June 24, 2026. 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…
When was CVE-2026-55570 disclosed?
CVE-2026-55570 was first published in the National Vulnerability Database on June 24, 2026, with the most recent update on June 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-55570 actively exploited?
CVE-2026-55570 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 24.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-55570?
CVE-2026-55570 has a CVSS v3 base score of 9.0 (NVD).
How do I remediate CVE-2026-55570?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-55570, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-55570

Explore →

Is Your Infrastructure Affected by CVE-2026-55570?

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

Start Free Scan →Browse All CVEs