CVE-2026-85174

HIGHPre-NVD 8.88.8—
EchelonGraph scoreHIGH confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-09-03. a secondary CVSS source baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this weekElevated
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.8Exploit: Elevated riskExposed: 0

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

SiYuan before v3.8.2 logs API tokens from query parameters in plaintext to an accessible log file when full-text search requests exceed timing thresholds. Authenticated attackers can read the log file via the getFile endpoint to recover admin API tokens and gain permanent administrative access.

CVSS v3
8.8
EG Score
8.8(high)
EG Risk
56(Track*)
EG Risk 56/100SSVC: Track*

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
Severity88% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
0%
EPSS %ILE
23%
KEV
Not listed

Published

September 3, 2026

Last Modified

September 8, 2026

Advisory Details (2)

Auto-updated Sep 3, 2026
Patch available. Sources: github.
generic

SiYuan before v3.8.2 API Token Exposure via Log File | Advisories | VulnCheck

https://www.vulncheck.com/advisories/siyuan-before-3.8.2-api-token-exposure-via-log-file
github Patch Available

API Token Exposed in Log File via token Query Parameter · Advisory · siyuan-note/siyuan · GitHub

https://github.com/siyuan-note/siyuan/security/advisories/GHSA-3wvc-5754-gp67

Vendor Advisories for CVE-2026-85174(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 27× in last 7d / 67× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-09-20 11:55 UTCGHSA enrichment
  2. 2026-09-19 23:38 UTCEG score recompute
  3. 2026-09-19 23:38 UTCGHSA enrichment
  4. 2026-09-19 11:43 UTCGHSA enrichment
  5. 2026-09-18 23:48 UTCEG score recompute
  6. 2026-09-18 23:48 UTCGHSA enrichment
  7. 2026-09-18 19:28 UTCEPSS rescore
  8. 2026-09-18 11:52 UTCGHSA enrichment
  9. 2026-09-17 23:57 UTCEG score recompute
  10. 2026-09-17 23:57 UTCGHSA enrichment
  11. 2026-09-17 19:32 UTCEPSS rescore
  12. 2026-09-17 11:10 UTCGHSA enrichment
  13. 2026-09-16 23:15 UTCEG score recompute
  14. 2026-09-16 23:15 UTCGHSA enrichment
  15. 2026-09-16 14:09 UTCEPSS rescore
  16. 2026-09-16 11:20 UTCEG score recompute
  17. 2026-09-16 11:20 UTCGHSA enrichment
  18. 2026-09-16 05:15 UTCEPSS rescore
  19. 2026-09-15 23:25 UTCGHSA enrichment
  20. 2026-09-15 11:27 UTCEG score recompute
  21. 2026-09-15 11:27 UTCGHSA enrichment
  22. 2026-09-15 03:12 UTCEPSS rescore
  23. 2026-09-15 03:12 UTCEPSS rescore
  24. 2026-09-14 23:32 UTCGHSA enrichment
  25. 2026-09-14 11:15 UTCGHSA enrichment
Show 42 more
  1. 2026-09-13 23:20 UTCEG score recompute
  2. 2026-09-13 23:20 UTCGHSA enrichment
  3. 2026-09-13 11:26 UTCGHSA enrichment
  4. 2026-09-12 23:31 UTCEG score recompute
  5. 2026-09-12 23:31 UTCGHSA enrichment
  6. 2026-09-12 11:36 UTCGHSA enrichment
  7. 2026-09-11 23:41 UTCEG score recompute
  8. 2026-09-11 23:41 UTCGHSA enrichment
  9. 2026-09-11 14:53 UTCEPSS rescore
  10. 2026-09-11 14:53 UTCEPSS rescore
  11. 2026-09-11 11:45 UTCEG score recompute
  12. 2026-09-11 11:45 UTCGHSA enrichment
  13. 2026-09-10 23:20 UTCGHSA enrichment
  14. 2026-09-10 11:25 UTCEG score recompute
  15. 2026-09-10 11:25 UTCGHSA enrichment
  16. 2026-09-09 23:29 UTCGHSA enrichment
  17. 2026-09-09 08:44 UTCEG score recompute
  18. 2026-09-09 08:44 UTCGHSA enrichment
  19. 2026-09-08 22:01 UTCEPSS rescore
  20. 2026-09-08 20:49 UTCGHSA enrichment
  21. 2026-09-08 02:45 UTCGHSA enrichment
  22. 2026-09-07 14:51 UTCGHSA enrichment
  23. 2026-09-07 02:06 UTCGHSA enrichment
  24. 2026-09-06 14:09 UTCEG score recompute
  25. 2026-09-06 14:09 UTCGHSA enrichment
  26. 2026-09-06 13:48 UTCEPSS rescore
  27. 2026-09-06 02:14 UTCEG score recompute
  28. 2026-09-06 02:14 UTCGHSA enrichment
  29. 2026-09-05 15:31 UTCEPSS rescore
  30. 2026-09-05 14:19 UTCGHSA enrichment
  31. 2026-09-05 02:24 UTCEG score recompute
  32. 2026-09-05 02:24 UTCGHSA enrichment
  33. 2026-09-05 01:34 UTCEG score recompute
  34. 2026-09-05 01:34 UTCGHSA enrichment
  35. 2026-09-05 01:02 UTCEG score recompute
  36. 2026-09-05 01:02 UTCGHSA enrichment
  37. 2026-09-04 13:06 UTCGHSA enrichment
  38. 2026-09-04 01:10 UTCEG score recompute
  39. 2026-09-04 01:10 UTCGHSA enrichment
  40. 2026-09-03 13:14 UTCEG score recompute
  41. 2026-09-03 11:31 UTCEG score recompute
  42. 2026-09-03 11:29 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-85174?
CVE-2026-85174 is a high vulnerability published on September 3, 2026. SiYuan before v3.8.2 logs API tokens from query parameters in plaintext to an accessible log file when full-text search requests exceed timing thresholds. Authenticated attackers can read the log file via the getFile endpoint to recover admin API tokens and gain permanent administrative access.
When was CVE-2026-85174 disclosed?
CVE-2026-85174 was first published in the National Vulnerability Database on September 3, 2026, with the most recent update on September 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-85174 actively exploited?
CVE-2026-85174 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 77.3% of all scored CVEs.
What is the CVSS score of CVE-2026-85174?
CVE-2026-85174 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-85174?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-85174, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-85174?

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

Start Free Scan →Browse All CVEs