CVE-2026-62204

MEDIUMPre-NVD 6.66.6—
EchelonGraph scoreHIGH confidence

Score 6.6 from GitHub Security Advisory published 2026-08-22. a secondary CVSS source baseline 6.6; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
6.6EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.6Exploit: None knownExposed: 0

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

SiYuan versions before v3.7.4 fail to validate that packageName matches the downloaded package content in bazaar install endpoints. Attackers with same-origin access can overwrite existing trusted plugins by supplying mismatched packageName and repoURL parameters, achieving persistence across application restarts.

CVSS v3
6.6
EG Score
6.6(high)
EG Risk
30(Track)
EG Risk 30/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
Severity66% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
0%
KEV
Not listed

Published

August 22, 2026

Last Modified

August 26, 2026

Advisory Details (2)

Auto-updated Aug 22, 2026
🔬 Proof of concept available. Patch available. Sources: github.
generic

SiYuan before v3.7.4 Plugin Overwrite via Bazaar Install | Advisories | VulnCheck

https://www.vulncheck.com/advisories/siyuan-before-plugin-overwrite-via-bazaar-install
github Patch Available🟡 PoC Available

Missing consistency check between packageName and repoURL/repoHash in bazaar package install allows overwriting an existing, trusted plugin · Advisory · siyuan-note/siyuan · GitHub

https://github.com/siyuan-note/siyuan/security/advisories/GHSA-rpx2-p6hp-x5gj

Vendor Advisories for CVE-2026-62204(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 / 16× 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-08-26 18:24 UTCEG score recompute
  2. 2026-08-26 18:24 UTCGHSA enrichment
  3. 2026-08-26 18:06 UTCEG score recompute
  4. 2026-08-26 18:05 UTCGHSA enrichment
  5. 2026-08-26 17:25 UTCGHSA enrichment
  6. 2026-08-26 16:14 UTCGHSA enrichment
  7. 2026-08-25 15:12 UTCEG score recompute
  8. 2026-08-25 15:12 UTCGHSA enrichment
  9. 2026-08-25 13:49 UTCEPSS rescore
  10. 2026-08-24 14:35 UTCEG score recompute
  11. 2026-08-24 14:34 UTCGHSA enrichment
  12. 2026-08-23 13:58 UTCEG score recompute
  13. 2026-08-23 13:58 UTCGHSA enrichment
  14. 2026-08-22 13:21 UTCEG score recompute
  15. 2026-08-22 12:46 UTCEG score recompute
  16. 2026-08-22 12:45 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-62204?
CVE-2026-62204 is a medium vulnerability published on August 22, 2026. SiYuan versions before v3.7.4 fail to validate that packageName matches the downloaded package content in bazaar install endpoints. Attackers with same-origin access can overwrite existing trusted plugins by supplying mismatched packageName and repoURL parameters, achieving persistence across…
When was CVE-2026-62204 disclosed?
CVE-2026-62204 was first published in the National Vulnerability Database on August 22, 2026, with the most recent update on August 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-62204 actively exploited?
CVE-2026-62204 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 100.0% of all scored CVEs.
What is the CVSS score of CVE-2026-62204?
CVE-2026-62204 has a CVSS v3 base score of 6.6 (NVD).
How do I remediate CVE-2026-62204?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-62204, 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-62204

Explore →

Is Your Infrastructure Affected by CVE-2026-62204?

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

Start Free Scan →Browse All CVEs