CVE-2026-79303

CRITICALPre-NVD 9.99.9—
EchelonGraph scoreHIGH confidence

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

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

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

kaiten from 57.192.20 to before 57.214.26 is vulnerable to SQL Injection. Dynamic SQL statements are generated without the required data validation and without using parameterized statements or stored procedures.

CVSS v3
9.9
EG Score
9.9(high)
EG Risk
61(Track*)
EG Risk 61/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
Severity99% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
0%
EPSS %ILE
34%
KEV
Not listed

Published

September 15, 2026

Last Modified

September 22, 2026

Advisory Details (1)

Auto-updated Sep 22, 2026
No patch confirmed yet.
generic

GitHub - 4ybrick/CVE-2026-79303: kaiten cve · GitHub

https://github.com/4ybrick/CVE-2026-79303

Vendor Advisories for CVE-2026-79303(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 32× in last 7d / 37× 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-25 06:31 UTCGHSA enrichment
  2. 2026-09-25 02:25 UTCGHSA enrichment
  3. 2026-09-24 22:18 UTCGHSA enrichment
  4. 2026-09-24 18:11 UTCEG score recompute
  5. 2026-09-24 18:11 UTCGHSA enrichment
  6. 2026-09-24 14:04 UTCEPSS rescore
  7. 2026-09-24 13:18 UTCGHSA enrichment
  8. 2026-09-24 09:12 UTCGHSA enrichment
  9. 2026-09-24 05:06 UTCGHSA enrichment
  10. 2026-09-24 00:59 UTCGHSA enrichment
  11. 2026-09-23 20:53 UTCEG score recompute
  12. 2026-09-23 20:53 UTCGHSA enrichment
  13. 2026-09-23 17:54 UTCEPSS rescore
  14. 2026-09-23 16:47 UTCGHSA enrichment
  15. 2026-09-23 12:40 UTCGHSA enrichment
  16. 2026-09-23 08:33 UTCGHSA enrichment
  17. 2026-09-23 04:27 UTCGHSA enrichment
  18. 2026-09-23 00:20 UTCGHSA enrichment
  19. 2026-09-22 20:13 UTCEG score recompute
  20. 2026-09-22 20:13 UTCGHSA enrichment
  21. 2026-09-22 16:24 UTCEG score recompute
  22. 2026-09-22 16:24 UTCGHSA enrichment
  23. 2026-09-22 16:01 UTCEPSS rescore
  24. 2026-09-22 15:20 UTCEG score recompute▲ 9.90
  25. 2026-09-22 15:20 UTCGHSA enrichment
Show 12 more
  1. 2026-09-22 15:19 UTCMITRE cvelistV5CVSS v3 → 9.9 · severity → CRITICAL
  2. 2026-09-22 00:25 UTCGHSA enrichment
  3. 2026-09-21 21:09 UTCEPSS rescore
  4. 2026-09-20 20:16 UTCEPSS rescore
  5. 2026-09-18 19:59 UTCEG score recompute
  6. 2026-09-18 19:59 UTCGHSA enrichment
  7. 2026-09-18 19:28 UTCEPSS rescore
  8. 2026-09-16 14:08 UTCEPSS rescore
  9. 2026-09-15 15:32 UTCGHSA enrichment
  10. 2026-09-15 15:31 UTCNVD update
  11. 2026-09-15 14:53 UTCEG score recompute
  12. 2026-09-15 14:52 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-79303?
CVE-2026-79303 is a critical vulnerability published on September 15, 2026. kaiten from 57.192.20 to before 57.214.26 is vulnerable to SQL Injection. Dynamic SQL statements are generated without the required data validation and without using parameterized statements or stored procedures.
When was CVE-2026-79303 disclosed?
CVE-2026-79303 was first published in the National Vulnerability Database on September 15, 2026, with the most recent update 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-79303 actively exploited?
CVE-2026-79303 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 65.5% of all scored CVEs.
What is the CVSS score of CVE-2026-79303?
CVE-2026-79303 has a CVSS v3.1 base score of 9.9 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-79303?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-79303, 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-79303

Explore →

Is Your Infrastructure Affected by CVE-2026-79303?

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

Book a Demo →Browse All CVEs