Sakura Editor provided by Sakura Editor Development Community contains an OS command injection vulnerability. If a victim user is directed to edit a file in a crafted directory, arbitrary OS command may be executed on the user's PC when the user invokes "Open Terminal".
CVE-2026-59561
Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-24. a secondary CVSS source baseline 7.8; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.8
- EG Score
- 7.8(high)
- EG Risk
- 35(Track)EG Risk 35/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 computedSeverity78% × 45%Exploitation1% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 1%
- EPSS %ILE
- 52%
- KEV
- Not listed
Published
August 24, 2026
Last Modified
August 28, 2026
Advisory Details (3)
Auto-updated Aug 24, 2026JVN#74538868: Sakura Editor vulnerable to OS command injection
https://jvn.jp/en/jp/JVN74538868/SAKURA Editor vulnerable to OS command injection (JVN#74538868) · Advisory · sakura-editor/sakura · GitHub
https://github.com/sakura-editor/sakura/security/advisories/GHSA-6x2x-729r-wjh5v2.4.3
Patch available: sakura-editor/sakura v2.4.3
https://github.com/sakura-editor/sakura/releases/tag/v2.4.3Vendor Advisories for CVE-2026-59561(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 28× in last 7d / 28× 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.
- 2026-08-30 05:53 UTCEG score recompute
- 2026-08-30 05:53 UTCGHSA enrichment
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 17:36 UTCGHSA enrichment
- 2026-08-29 04:33 UTCEG score recompute
- 2026-08-29 04:32 UTCGHSA enrichment
- 2026-08-28 21:42 UTCEPSS rescore
- 2026-08-28 16:15 UTCGHSA enrichment
- 2026-08-28 07:19 UTCGHSA enrichment
- 2026-08-27 18:59 UTCEG score recompute
- 2026-08-27 18:58 UTCGHSA enrichment
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-27 06:41 UTCGHSA enrichment
- 2026-08-26 18:26 UTCEG score recompute
- 2026-08-26 18:26 UTCGHSA enrichment
- 2026-08-26 14:46 UTCEPSS rescore
- 2026-08-26 06:07 UTCGHSA enrichment
- 2026-08-25 17:48 UTCEG score recompute
- 2026-08-25 17:48 UTCGHSA enrichment
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-25 05:33 UTCGHSA enrichment
- 2026-08-24 17:19 UTCEG score recompute
- 2026-08-24 17:19 UTCGHSA enrichment
- 2026-08-24 16:52 UTCEG score recompute
- 2026-08-24 16:52 UTCGHSA enrichment
Show 3 moreShow fewer
- 2026-08-24 05:24 UTCEG score recompute
- 2026-08-24 05:11 UTCEG score recompute
- 2026-08-24 05:10 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-59561?
When was CVE-2026-59561 disclosed?
Is CVE-2026-59561 actively exploited?
What is the CVSS score of CVE-2026-59561?
How do I remediate CVE-2026-59561?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-59561
Is Your Infrastructure Affected by CVE-2026-59561?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.