CVE-2026-34449

CRITICALNVD 9.69.6
EchelonGraph scoreMEDIUM confidence

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

Score 9.6 from GitHub Security Advisory (severity: CRITICAL) published 2026-03-31. NVD baseline CVSS 9.6; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Elevated

Also known asEUVD-2026-17676 (ENISA EUVD) · GHSA-68p4-j234-43mv (GitHub Security Advisories) · GO-2026-5171 (OSV.dev)Source: ENISA EUVD

9.6EG
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.6Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

SiYuan is a personal knowledge management system. Prior to version 3.6.2, a malicious website can achieve Remote Code Execution (RCE) on any desktop running SiYuan by exploiting the permissive CORS policy (Access-Control-Allow-Origin: * + Access-Control-Allow-Private-Network: true) to inject a JavaScript snippet via the API. The injected snippet executes in Electron's Node.js context with full OS access the next time the user opens SiYuan's UI. No user interaction is required beyond visiting the malicious website while SiYuan is running. This issue has been patched in version 3.6.2.

CVSS v3
9.6
EG Score
9.6CRITICALmedium confidence
EG Risk
59
EG Risk 59/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)
Severity96% × 45%
Impact severity (EG Severity): CVSS 9.6 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: 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
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.6): severity, escalated by confirmed exploitation. This CVE's 9.6 is its impact severity (EG Severity), not escalated.

EG Severity
9.6 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-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.

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). 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

March 31, 2026

Last Modified

July 24, 2026

Advisory Details (3)

Auto-updated Oct 7, 2026
Patch available. Sources: github_release, github.
GitHub advisoryMentions a patch (unverified)

Cross-Origin RCE via Permissive CORS Policy and JavaScript Snippet Injection · Advisory · siyuan-note/siyuan · GitHub

https://github.com/siyuan-note/siyuan/security/advisories/GHSA-68p4-j234-43mv
GitHub release Patch Available

Improve details

Patch available: siyuan-note/siyuan v3.6.2

https://github.com/siyuan-note/siyuan/releases/tag/v3.6.2
Web page

Fix some security vulnerabilities · Issue #17246 · siyuan-note/siyuan · GitHub

https://github.com/siyuan-note/siyuan/issues/17246

Vendor Advisories for CVE-2026-34449(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 @ 3.6.2 (fixes <= 3.6.1)—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 up to 3.6.2: fixed in 3.6.2
  • every version on: no fix on record
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 13× in last 7d / 44× 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 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). "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 272 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 172 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-34449?
CVE-2026-34449 is a critical-severity vulnerability; its CVE record was published on March 31, 2026. SiYuan is a personal knowledge management system. Prior to version 3.6.2, a malicious website can achieve Remote Code Execution (RCE) on any desktop running SiYuan by exploiting the permissive CORS policy (Access-Control-Allow-Origin: * + Access-Control-Allow-Private-Network: true) to inject a…
When was the CVE record for CVE-2026-34449 published?
The CVE record for CVE-2026-34449 was published on March 31, 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 July 24, 2026; the record at its source may have been updated since.
Is CVE-2026-34449 actively exploited?
CVE-2026-34449 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-34449?
CVE-2026-34449 has a CVSS v3 base score of 9.6 (NVD).
How do I remediate CVE-2026-34449?
A fix for CVE-2026-34449 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-34449 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-34449

Explore →

Is Your Infrastructure Affected by CVE-2026-34449?

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