CVE-2026-67917

CRITICALPre-NVD 9.89.8
EchelonGraph scoreHIGH confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-17. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 5 sources updated this weekElevated
9.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: 9.8Exploit: Elevated riskExposed: 0

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

zuraCast versions up to and including 0.23.7 contain a SQL injection vulnerability in the backup restore functionality. The azuracast:restore command executes the db.sql file extracted from a backup archive without any content validation or sanitization. This allows a remote attacker to escalate privileges

CVSS v3
9.8
EG Score
9.8(high)
EG Risk
75(Attend)
EG Risk 75/100SSVC: Attend

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
Severity98% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
34%
KEV
Not listed

Published

August 17, 2026

Last Modified

August 18, 2026

Advisory Details (2)

Auto-updated Aug 18, 2026
No patch confirmed yet.
generic

SQL-Injection-PoC/SQL-Injection-PoC at main · luoxuanxi/SQL-Injection-PoC · GitHub

https://github.com/luoxuanxi/SQL-Injection-PoC/tree/main/SQL-Injection-PoC
generic

GitHub - luoxuanxi/SQL-Injection-PoC: PoC for SQL Injection vulnerability in AzuraCast backup restore · GitHub

https://github.com/luoxuanxi/SQL-Injection-PoC

Vendor Advisories for CVE-2026-67917(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 30× in last 7d / 30× 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-21 06:47 UTCGHSA enrichment
  2. 2026-08-21 02:44 UTCEG score recompute
  3. 2026-08-21 02:44 UTCGHSA enrichment
  4. 2026-08-20 22:56 UTCEPSS rescore
  5. 2026-08-20 22:41 UTCGHSA enrichment
  6. 2026-08-20 18:38 UTCGHSA enrichment
  7. 2026-08-20 14:35 UTCGHSA enrichment
  8. 2026-08-20 10:32 UTCGHSA enrichment
  9. 2026-08-20 06:30 UTCGHSA enrichment
  10. 2026-08-20 02:27 UTCGHSA enrichment
  11. 2026-08-19 22:24 UTCGHSA enrichment
  12. 2026-08-19 18:20 UTCEG score recompute
  13. 2026-08-19 18:20 UTCGHSA enrichment
  14. 2026-08-19 17:04 UTCEPSS rescore
  15. 2026-08-19 13:06 UTCGHSA enrichment
  16. 2026-08-19 09:03 UTCGHSA enrichment
  17. 2026-08-19 04:57 UTCGHSA enrichment
  18. 2026-08-19 00:52 UTCGHSA enrichment
  19. 2026-08-18 20:48 UTCEG score recompute
  20. 2026-08-18 20:48 UTCGHSA enrichment
  21. 2026-08-18 16:46 UTCEG score recompute
  22. 2026-08-18 16:46 UTCGHSA enrichment
  23. 2026-08-18 15:59 UTCEG score recompute 9.80
  24. 2026-08-18 15:59 UTCGHSA enrichment
  25. 2026-08-18 15:59 UTCMITRE cvelistV5CVSS v3 → 9.8 · severity → CRITICAL
Show 5 more
  1. 2026-08-18 13:48 UTCEPSS rescore
  2. 2026-08-17 21:32 UTCGHSA enrichment
  3. 2026-08-17 21:29 UTCNVD update
  4. 2026-08-17 20:55 UTCEG score recompute
  5. 2026-08-17 20:54 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-67917?
CVE-2026-67917 is a critical vulnerability published on August 17, 2026. zuraCast versions up to and including 0.23.7 contain a SQL injection vulnerability in the backup restore functionality. The azuracast:restore command executes the db.sql file extracted from a backup archive without any content validation or sanitization. This allows a remote attacker to escalate…
When was CVE-2026-67917 disclosed?
CVE-2026-67917 was first published in the National Vulnerability Database on August 17, 2026, with the most recent update on August 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-67917 actively exploited?
CVE-2026-67917 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 66.0% of all scored CVEs.
What is the CVSS score of CVE-2026-67917?
CVE-2026-67917 has a CVSS v3.1 base score of 9.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-67917?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-67917, 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-67917

Explore →

Is Your Infrastructure Affected by CVE-2026-67917?

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