CVE-2026-44588

CRITICALNVD 9.49.4
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.4 under NVD CVSS. EPSS exploit probability: 0.5% (43rd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS
Sources: EPSS, NVD CVSS
Elevated

Also known asEUVD-2026-30359 (ENISA EUVD) · GHSA-25rp-h46x-2hjm (GitHub Security Advisories) · GO-2026-4993 (OSV.dev)Source: ENISA EUVD

9.4EG
EchelonGraph verdictPlan a fixRemediate 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.4Exploit: No code on recordExposed services: Not assessed

The CVE record names the fixed release — apply it.

SiYuan is an open-source personal knowledge management system. Prior to 3.7.0, he tooltip mouseover handler in app/src/block/popover.ts reads aria-label via getAttribute and passes it through decodeURIComponent before assigning to messageElement.innerHTML in app/src/dialog/tooltip.ts:41. The encoder used at the producer side, escapeAriaLabel in app/src/util/escape.ts:19-25, only handles HTML special characters (", ', <, literal <) — it leaves %XX URL-escapes untouched. So a doc title containing %3Cimg src=x onerror=...%3E round-trips through escapeAriaLabel and the HTML attribute layer unmodified. Then decodeURIComponent on the consumer side converts %3C to a literal < character (a real <, NOT a character reference). When that string is assigned to innerHTML, the HTML5 tokenizer enters TagOpenState on the literal <, parses the element, and the onerror handler fires. Because the renderer runs with nodeIntegration: true, contextIsolation: false, webSecurity: false (app/electron/main.js:407-411), require('child_process') is reachable from the injected handler, escalating to arbitrary code execution.This vulnerability is fixed in 3.7.0.

CVSS
9.4
EG Score
9.4CRITICALmedium confidence
EG Risk
58
EG Risk 58/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)
Severity94% × 45%
Impact severity (EG Severity): CVSS 9.4 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: The CVE record names the fixed release. 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
43rd
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.4): severity, escalated by confirmed exploitation. This CVE's 9.4 is its impact severity (EG Severity), not escalated.

EG Severity
9.4 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). 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, and whom BOD 26-04 binds: 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.

The CVE record names the fixed release. 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). 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.

The score's inputs: 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

May 14, 2026

Last Modified

May 15, 2026

Advisory Details (1)

Auto-updated Oct 2, 2026
Fix named in the CVE record. Sources: github.
GitHub advisoryMentions a patch (unverified)

URL-encoded title bypasses `escapeAriaLabel`, decoded by `decodeURIComponent` into a tooltip-XSS => Electron renderer RCE in SiYuan · Advisory · siyuan-note/siyuan · GitHub

https://github.com/siyuan-note/siyuan/security/advisories/GHSA-25rp-h46x-2hjm

Vendor Advisories for CVE-2026-44588(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

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/siyuan-note/siyuan/kernel—
  • every version through 0.0.0-20260421031503-96dfe0bea474: no fix on record
  • every version on: no fix on record
—

Weakness Classification(3)

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

Data Freshness Timeline

(refreshed 13× in last 7d / 59× 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 its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 427 rows 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 327 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-44588?
CVE-2026-44588 is a critical-severity vulnerability; its CVE record was published on May 14, 2026. SiYuan is an open-source personal knowledge management system. Prior to 3.7.0, he tooltip mouseover handler in app/src/block/popover.ts reads aria-label via getAttribute and passes it through decodeURIComponent before assigning to messageElement.innerHTML in app/src/dialog/tooltip.ts:41. The…
When was the CVE record for CVE-2026-44588 published?
The CVE record for CVE-2026-44588 was published on May 14, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of May 15, 2026; the record at its source may have been updated since.
Is CVE-2026-44588 actively exploited?
CVE-2026-44588 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (43rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-44588?
CVE-2026-44588 has a CVSS base score of 9.4 (NVD).
How do I remediate CVE-2026-44588?
The CVE record for CVE-2026-44588 names the fix: "…This vulnerability is fixed in 3.7.0." The vendor advisories EchelonGraph has for CVE-2026-44588 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-44588

Explore →

Is Your Infrastructure Affected by CVE-2026-44588?

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

Book a Demo →Browse All CVEs