CVE-2026-73053

CRITICALPre-NVD 9.09.0
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 9.0 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-16. A secondary CVSS source baseline 9.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this weekElevated
9.0EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 9.0Exploit: No code on recordExposed services: Not assessed

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

The CVE record's CNA (VulnCheck) lists siyuan-note siyuan versions before 3.7.4 as affected, and siyuan-note siyuan versions 3.7.4 as unaffected. No release containing a fix is confirmed on record.

SiYuan versions before v3.7.4 contain a cross-site scripting vulnerability in the unicode2Emoji function that fails to sanitize codepoint branch output. Attackers can craft document icons with hex-encoded markup that executes in the renderer with Node integration enabled, achieving arbitrary code execution on the host system.

CVSS v3
9.0
EG Score
9.0CRITICALmedium confidence
EG Risk
57
EG Risk 57/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity90% × 45%
Impact severity (EG Severity): CVSS 9.0 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.5%
EPSS %ILE
42nd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.0): severity, escalated by confirmed exploitation. This CVE's 9.0 is its impact severity (EG Severity), not escalated.

EG Severity
9.0 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-19). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 15, 2026

Last Modified

August 26, 2026

Advisory Details (2)

Auto-updated Aug 15, 2026
No fix on record yet. Sources: github.
Web page

SiYuan before v3.7.4 Cross-Site Scripting via unicode2Emoji | Advisories | VulnCheck

https://www.vulncheck.com/advisories/siyuan-before-cross-site-scripting-via-unicode2emoji
GitHub advisoryMentions a patch (unverified)

A single unsanitized branch in unicode2Emoji turns a document icon into Remote Code Execution on the desktop client · Advisory · siyuan-note/siyuan · GitHub

https://github.com/siyuan-note/siyuan/security/advisories/GHSA-vx5w-qrvp-mmcq

Vendor Advisories for CVE-2026-73053(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 21× in last 7d / 125× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 380 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 280 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-73053?
CVE-2026-73053 is a critical-severity vulnerability; its CVE record was published on August 15, 2026. SiYuan versions before v3.7.4 contain a cross-site scripting vulnerability in the unicode2Emoji function that fails to sanitize codepoint branch output. Attackers can craft document icons with hex-encoded markup that executes in the renderer with Node integration enabled, achieving arbitrary code…
When was CVE-2026-73053 made public?
CVE-2026-73053 was made public on August 1, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on August 15, 2026. EchelonGraph's copy of the record carries a last-modified date of August 26, 2026; the record at its source may have been updated since.
Is CVE-2026-73053 actively exploited?
CVE-2026-73053 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (42nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-73053?
CVE-2026-73053 has a CVSS base score of 9.0 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-73053?
No fix for CVE-2026-73053 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The CVE record's CNA (VulnCheck) lists siyuan-note siyuan versions before 3.7.4 as affected, and siyuan-note siyuan versions 3.7.4 as unaffected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-73053 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-73053?

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