CVE-2026-79617

HIGHPre-NVD 7.17.1
EchelonGraph scoreHIGH confidence

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2026-09-09. a secondary CVSS source baseline 7.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.1EG
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.1Exploit: None knownExposed: 0

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

Incorrect Permission Assignment for Critical Resource vulnerability in TÜBİTAK BİLGEM Software Technologies Research Institute Pardus LightDM Greeter allows Exploiting Incorrectly Configured Access Control Security Levels.

This issue affects Pardus LightDM Greeter: before 0.4.15.

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

Published

September 9, 2026

Last Modified

September 9, 2026

Advisory Details (1)

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

Vendor Advisories for CVE-2026-79617(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-21 00:37 UTCEG score recompute
  2. 2026-09-21 00:37 UTCGHSA enrichment
  3. 2026-09-20 20:16 UTCEPSS rescore
  4. 2026-09-20 11:53 UTCGHSA enrichment
  5. 2026-09-19 23:10 UTCEG score recompute
  6. 2026-09-19 23:10 UTCGHSA enrichment
  7. 2026-09-19 10:25 UTCGHSA enrichment
  8. 2026-09-18 21:42 UTCEG score recompute
  9. 2026-09-18 21:42 UTCGHSA enrichment
  10. 2026-09-18 19:28 UTCEPSS rescore
  11. 2026-09-18 08:58 UTCGHSA enrichment
  12. 2026-09-17 20:14 UTCEG score recompute
  13. 2026-09-17 20:14 UTCGHSA enrichment
  14. 2026-09-17 06:55 UTCGHSA enrichment
  15. 2026-09-16 18:11 UTCEG score recompute
  16. 2026-09-16 18:11 UTCGHSA enrichment
  17. 2026-09-16 14:08 UTCEPSS rescore
  18. 2026-09-16 05:28 UTCEG score recompute
  19. 2026-09-16 05:28 UTCGHSA enrichment
  20. 2026-09-16 05:15 UTCEPSS rescore
  21. 2026-09-15 16:44 UTCGHSA enrichment
  22. 2026-09-15 04:00 UTCEG score recompute
  23. 2026-09-15 04:00 UTCGHSA enrichment
  24. 2026-09-15 03:12 UTCEPSS rescore
  25. 2026-09-15 03:12 UTCEPSS rescore
Show 24 more
  1. 2026-09-14 15:14 UTCGHSA enrichment
  2. 2026-09-14 02:31 UTCEG score recompute
  3. 2026-09-14 02:31 UTCGHSA enrichment
  4. 2026-09-13 13:47 UTCGHSA enrichment
  5. 2026-09-13 01:04 UTCEG score recompute
  6. 2026-09-13 01:04 UTCGHSA enrichment
  7. 2026-09-12 12:20 UTCGHSA enrichment
  8. 2026-09-11 23:36 UTCEG score recompute
  9. 2026-09-11 23:36 UTCGHSA enrichment
  10. 2026-09-11 14:53 UTCEPSS rescore
  11. 2026-09-11 14:53 UTCEPSS rescore
  12. 2026-09-11 10:52 UTCEG score recompute
  13. 2026-09-11 10:52 UTCGHSA enrichment
  14. 2026-09-10 22:08 UTCGHSA enrichment
  15. 2026-09-10 09:24 UTCGHSA enrichment
  16. 2026-09-09 20:38 UTCEG score recompute
  17. 2026-09-09 20:38 UTCGHSA enrichment
  18. 2026-09-09 19:21 UTCEG score recompute
  19. 2026-09-09 19:21 UTCGHSA enrichment
  20. 2026-09-09 15:47 UTCEG score recompute
  21. 2026-09-09 15:47 UTCGHSA enrichment
  22. 2026-09-09 15:28 UTCEG score recompute
  23. 2026-09-09 14:20 UTCEG score recompute
  24. 2026-09-09 14:20 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-79617?
CVE-2026-79617 is a high vulnerability published on September 9, 2026. Incorrect Permission Assignment for Critical Resource vulnerability in TÜBİTAK BİLGEM Software Technologies Research Institute Pardus LightDM Greeter allows Exploiting Incorrectly Configured Access Control Security Levels. This issue affects Pardus LightDM Greeter: before 0.4.15.
When was CVE-2026-79617 disclosed?
CVE-2026-79617 was first published in the National Vulnerability Database 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-79617 actively exploited?
CVE-2026-79617 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 96.5% of all scored CVEs.
What is the CVSS score of CVE-2026-79617?
CVE-2026-79617 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-79617?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-79617, 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-79617

Explore →

Is Your Infrastructure Affected by CVE-2026-79617?

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