CVE-2026-60084

HIGHPre-NVD 8.78.7
EchelonGraph scoreMEDIUM confidence

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

Score 8.7 from GitHub Security Advisory (severity: HIGH) published 2026-08-22. A secondary CVSS source baseline 8.7; 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
8.7EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (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.4%CVSS: 8.7Exploit: 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 an arbitrary file deletion vulnerability in the /api/search/removeTemplate endpoint that accepts an unvalidated path parameter passed directly to os.RemoveAll. Authenticated admin attackers can supply absolute filesystem paths to recursively delete any file or directory the kernel process has permission to remove, anywhere on the host filesystem.

CVSS v3
8.7
EG Score
8.7HIGHmedium confidence
EG Risk
55
EG Risk 55/100

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 (value × EchelonGraph’s weight)
Severity87% × 45%
The EG Score, 8.7 of 10.
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 or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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, and watch the vendor's advisory for the fix.
EPSS PROB
0.4%
EPSS %ILE
32nd
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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)60 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 partial (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 22, 2026

Last Modified

October 12, 2026

Advisory Details (2)

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

SiYuan before v3.7.4 Arbitrary File Deletion via removeTemplate | Advisories | VulnCheck

https://www.vulncheck.com/advisories/siyuan-before-arbitrary-file-deletion-via-removetemplate
GitHub advisoryMentions a patch (unverified)

Unrestricted arbitrary file/directory deletion via /api/search/removeTemplate: the client-supplied "path" parameter is passed directly to os.RemoveAll with no validation and no base-directory restriction · Advisory · siyuan-note/siyuan · GitHub

Affected: 2025) and from

https://github.com/siyuan-note/siyuan/security/advisories/GHSA-w938-w7m4-qrj8

Vendor Advisories for CVE-2026-60084(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 16× in last 7d / 94× 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 180 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 80 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-60084?
CVE-2026-60084 is a high-severity vulnerability; its CVE record was published on August 22, 2026. SiYuan versions before v3.7.4 contain an arbitrary file deletion vulnerability in the /api/search/removeTemplate endpoint that accepts an unvalidated path parameter passed directly to os.RemoveAll. Authenticated admin attackers can supply absolute filesystem paths to recursively delete any file or…
When was CVE-2026-60084 made public?
CVE-2026-60084 was made public on August 8, 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 22, 2026. EchelonGraph's copy of the record carries a last-modified date of October 12, 2026; the record at its source may have been updated since.
Is CVE-2026-60084 actively exploited?
CVE-2026-60084 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (32nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-60084?
CVE-2026-60084 has a CVSS base score of 8.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-60084?
No fix for CVE-2026-60084 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-60084 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-60084?

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

Book a Demo →Browse All CVEs