CVE-2026-85585

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-09-04. A secondary CVSS source baseline 7.5; 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
7.5EG
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: 7.5Exploit: 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.

SiYuan before v3.8.2 contains an unbounded resource consumption vulnerability in the request-concurrency middleware that retains mutex entries for every unique request path without eviction. Unauthenticated attackers can send numerous unique request paths to permanently increase process memory and synchronization overhead, degrading availability.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
65
EG Risk 65/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)
Severity75% × 45%
The EG Score, 7.5 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (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 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
41st
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend 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 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 yes (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)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (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

September 4, 2026

Last Modified

September 8, 2026

Advisory Details (2)

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

SiYuan before v3.8.2 Unbounded Memory Consumption via ControlConcurrency | Advisories | VulnCheck

https://www.vulncheck.com/advisories/siyuan-before-3.8.2-unbounded-memory-consumption-via-controlconcurrency
GitHub advisoryMentions a patch (unverified)

Unauthenticated unique request paths grow the global ControlConcurrency map without bound · Advisory · siyuan-note/siyuan · GitHub

https://github.com/siyuan-note/siyuan/security/advisories/GHSA-p59v-3q54-qq55

Vendor Advisories for CVE-2026-85585(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 26× in last 7d / 114× 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 146 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 46 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-85585?
CVE-2026-85585 is a high-severity vulnerability; its CVE record was published on September 4, 2026. SiYuan before v3.8.2 contains an unbounded resource consumption vulnerability in the request-concurrency middleware that retains mutex entries for every unique request path without eviction. Unauthenticated attackers can send numerous unique request paths to permanently increase process memory and…
When was CVE-2026-85585 made public?
CVE-2026-85585 was made public on August 21, 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 September 4, 2026. EchelonGraph's copy of the record carries a last-modified date of September 8, 2026; the record at its source may have been updated since.
Is CVE-2026-85585 actively exploited?
CVE-2026-85585 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (41st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-85585?
CVE-2026-85585 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-85585?
No fix for CVE-2026-85585 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 vendor advisories EchelonGraph has for CVE-2026-85585 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-85585?

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

Book a Demo →Browse All CVEs