CVE-2026-79575

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 3 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

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

The JWT signing secret in yfexam-exam v2.0 is derived from the username and the current month instead of a random server-side key, making the secret key easily obtainable via a bruteforce attack.

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

Published

September 8, 2026

Last Modified

September 9, 2026

Advisory Details (1)

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

CVE/yf-exam/JWT.md at main · fangtang7/CVE · GitHub

https://github.com/fangtang7/CVE/blob/main/yf-exam/JWT.md

Vendor Advisories for CVE-2026-79575(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 / 49× 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-19 17:13 UTCEG score recompute
  2. 2026-09-19 17:12 UTCGHSA enrichment
  3. 2026-09-19 05:59 UTCEG score recompute
  4. 2026-09-19 05:58 UTCGHSA enrichment
  5. 2026-09-18 19:28 UTCEPSS rescore
  6. 2026-09-18 18:46 UTCGHSA enrichment
  7. 2026-09-18 07:33 UTCGHSA enrichment
  8. 2026-09-17 20:20 UTCEG score recompute
  9. 2026-09-17 20:20 UTCGHSA enrichment
  10. 2026-09-17 05:33 UTCGHSA enrichment
  11. 2026-09-16 18:19 UTCEG score recompute
  12. 2026-09-16 18:19 UTCGHSA enrichment
  13. 2026-09-16 14:08 UTCEPSS rescore
  14. 2026-09-16 05:30 UTCEG score recompute
  15. 2026-09-16 05:30 UTCGHSA enrichment
  16. 2026-09-16 05:15 UTCEPSS rescore
  17. 2026-09-15 18:17 UTCGHSA enrichment
  18. 2026-09-15 06:44 UTCEG score recompute
  19. 2026-09-15 06:44 UTCGHSA enrichment
  20. 2026-09-15 03:12 UTCEPSS rescore
  21. 2026-09-15 03:12 UTCEPSS rescore
  22. 2026-09-14 19:31 UTCGHSA enrichment
  23. 2026-09-14 08:18 UTCGHSA enrichment
  24. 2026-09-13 21:05 UTCEG score recompute
  25. 2026-09-13 21:05 UTCGHSA enrichment
Show 24 more
  1. 2026-09-13 09:52 UTCGHSA enrichment
  2. 2026-09-12 22:39 UTCEG score recompute
  3. 2026-09-12 22:39 UTCGHSA enrichment
  4. 2026-09-12 11:26 UTCGHSA enrichment
  5. 2026-09-12 00:13 UTCEG score recompute
  6. 2026-09-12 00:13 UTCGHSA enrichment
  7. 2026-09-11 14:53 UTCEPSS rescore
  8. 2026-09-11 14:53 UTCEPSS rescore
  9. 2026-09-11 13:00 UTCEG score recompute
  10. 2026-09-11 13:00 UTCGHSA enrichment
  11. 2026-09-11 01:47 UTCGHSA enrichment
  12. 2026-09-10 14:34 UTCEG score recompute
  13. 2026-09-10 14:34 UTCGHSA enrichment
  14. 2026-09-10 03:21 UTCGHSA enrichment
  15. 2026-09-09 16:08 UTCEG score recompute
  16. 2026-09-09 16:08 UTCGHSA enrichment
  17. 2026-09-09 15:31 UTCGHSA enrichment
  18. 2026-09-09 15:05 UTCEG score recompute▲ 7.50
  19. 2026-09-09 15:05 UTCGHSA enrichment
  20. 2026-09-09 15:04 UTCMITRE cvelistV5CVSS v3 → 7.5 · severity → HIGH
  21. 2026-09-08 15:42 UTCGHSA enrichment
  22. 2026-09-08 15:27 UTCNVD update
  23. 2026-09-08 15:05 UTCEG score recompute
  24. 2026-09-08 15:04 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-79575?
CVE-2026-79575 is a high vulnerability published on September 8, 2026. The JWT signing secret in yfexam-exam v2.0 is derived from the username and the current month instead of a random server-side key, making the secret key easily obtainable via a bruteforce attack.
When was CVE-2026-79575 disclosed?
CVE-2026-79575 was first published in the National Vulnerability Database on September 8, 2026, with the most recent update on September 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-79575 actively exploited?
CVE-2026-79575 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 84.0% of all scored CVEs.
What is the CVSS score of CVE-2026-79575?
CVE-2026-79575 has a CVSS v3.1 base score of 7.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-79575?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-79575, 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-79575

Explore →

Is Your Infrastructure Affected by CVE-2026-79575?

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

Start Free Scan →Browse All CVEs