CVE-2026-82233

MEDIUMPre-NVD 5.75.7
EchelonGraph scoreMEDIUM confidence

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

Score 5.7 from GitHub Security Advisory published 2026-08-28. A secondary CVSS source baseline 5.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
5.7EG
EchelonGraph verdictPlan a fixRemediate 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: 5.7Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

SiYuan before v3.8.1 contains a path traversal vulnerability in the asset.upload MCP tool that accepts arbitrary absolute file paths without workspace boundary validation. Attackers can induce the AI Agent to upload sensitive files such as SSH keys or credentials from outside the workspace into the asset directory through prompt injection.

CVSS v3
5.7
EG Score
5.7MEDIUMmedium confidence
EG Risk
42
EG Risk 42/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)
Severity57% × 45%
The EG Score, 5.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: A fix is available. Apply it within your standard update timelines.
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).

A fix is available. Apply it within your standard update timelines.

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 28, 2026

Last Modified

August 31, 2026

Advisory Details (2)

Auto-updated Aug 28, 2026
Patch available. Sources: github.
Web page

SiYuan before v3.8.1 Path Traversal via asset.upload | Advisories | VulnCheck

https://www.vulncheck.com/advisories/siyuan-before-3.8.1-path-traversal-via-asset-upload
GitHub advisoryMentions a patch (unverified)

SiYuan MCP asset.upload Reads Arbitrary Absolute File Paths (Workspace Boundary Bypass) · Advisory · siyuan-note/siyuan · GitHub

https://github.com/siyuan-note/siyuan/security/advisories/GHSA-p23f-cm6q-2qp8

Vendor Advisories for CVE-2026-82233(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/siyuan-note/siyuan/kernel—
  • every version up to 0.0.0-20260813142104-b26a4a307b8a: fixed in 0.0.0-20260813142104-b26a4a307b8a
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 17× in last 7d / 75× 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 98 of 122 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. 2 repeat rows among the latest 100 are merged into the row they repeat. The 24 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-82233?
CVE-2026-82233 is a medium-severity vulnerability; its CVE record was published on August 28, 2026. SiYuan before v3.8.1 contains a path traversal vulnerability in the asset.upload MCP tool that accepts arbitrary absolute file paths without workspace boundary validation. Attackers can induce the AI Agent to upload sensitive files such as SSH keys or credentials from outside the workspace into the…
When was CVE-2026-82233 made public?
CVE-2026-82233 was made public on August 13, 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 28, 2026. EchelonGraph's copy of the record carries a last-modified date of August 31, 2026; the record at its source may have been updated since.
Is CVE-2026-82233 actively exploited?
CVE-2026-82233 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-82233?
CVE-2026-82233 has a CVSS base score of 5.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-82233?
A fix for CVE-2026-82233 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-82233 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-82233

Explore →

Is Your Infrastructure Affected by CVE-2026-82233?

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

Book a Demo →Browse All CVEs