CVE-2026-95624

MEDIUMPre-NVD 6.86.8—
EchelonGraph scoreHIGH confidence

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

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

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

The Tauri updater plugin's 'check' IPC command accepts an allowDowngrades boolean parameter directly from frontend JavaScript code. When set to true, it replaces the version comparator from "update must be newer" to "update must be different." Because the default permission set grants allow-check to the webview, any XSS in the app frontend can invoke this command and bypass the only anti-rollback protection the updater offers. Combined with another bug, this enables downgrade attacks without even needing to fake a higher version number.

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

Published

September 22, 2026

Last Modified

September 22, 2026

Advisory Details (3)

Auto-updated Sep 22, 2026
Patch available. Sources: github_commit, github_release.
github_release Patch Available

updater v2.12.0

Patch available: tauri-apps/plugins-workspace updater-v2.12.0

https://github.com/tauri-apps/plugins-workspace/releases/tag/updater-v2.12.0
github_commit Patch Available

commit 1308bfa399b9 (tauri-apps/plugins-workspace)

Patch available: tauri-apps/plugins-workspace opener-v3.0.0-alpha.1 (contains commit 1308bfa399b9)

https://github.com/tauri-apps/plugins-workspace/commit/1308bfa399b962b3977c767100a6339d1cbfdd20
generic

GitHub - tauri-apps/tauri: Build smaller, faster, and more secure desktop and mobile applications with a web frontend. · GitHub

https://github.com/tauri-apps/tauri

Vendor Advisories for CVE-2026-95624(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 10× in last 7d / 10× 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-23 19:16 UTCEG score recompute
  2. 2026-09-23 19:16 UTCGHSA enrichment
  3. 2026-09-23 17:54 UTCEPSS rescore
  4. 2026-09-22 20:33 UTCEG score recompute
  5. 2026-09-22 20:33 UTCGHSA enrichment
  6. 2026-09-22 19:38 UTCEG score recompute
  7. 2026-09-22 19:38 UTCGHSA enrichment
  8. 2026-09-22 18:32 UTCEG score recompute
  9. 2026-09-22 17:25 UTCEG score recompute
  10. 2026-09-22 17:23 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-95624?
CVE-2026-95624 is a medium vulnerability published on September 22, 2026. The Tauri updater plugin's 'check' IPC command accepts an allowDowngrades boolean parameter directly from frontend JavaScript code. When set to true, it replaces the version comparator from "update must be newer" to "update must be different." Because the default permission set grants allow-check…
When was CVE-2026-95624 disclosed?
CVE-2026-95624 was first published in the National Vulnerability Database on September 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-95624 actively exploited?
CVE-2026-95624 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 61.6% of all scored CVEs.
What is the CVSS score of CVE-2026-95624?
CVE-2026-95624 has a CVSS v3 base score of 6.8 (NVD).
How do I remediate CVE-2026-95624?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-95624, 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-95624

Explore →

Is Your Infrastructure Affected by CVE-2026-95624?

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

Book a Demo →Browse All CVEs