CVE-2026-58502

HIGHPre-NVD 7.17.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (44th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated

Also known asEUVD-2026-78911 (ENISA EUVD)Source: ENISA EUVD

7.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 7.1Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

githubtoplanguages generates a user's top GitHub languages as an SVG. The .github/workflows/discord-issue.yml workflow runs when an issue is opened or closed and interpolates github.event.issue.title directly into the Bash assignment for ISSUE_TITLE before shell parsing. An issue title containing shell command-substitution syntax can therefore execute commands on the GitHub Actions runner before the title is included in the Discord notification sent through DISCORD_WEBHOOK. Successful exploitation can manipulate or spoof trusted bot notifications and may expose the Discord webhook secret or other workflow environment data, depending on repository permissions. This issue is fixed by commit 6bf9c3a9cb66c937b9047ca266b3d02f2bb11027.

CVSS v3
7.1
EG Score
7.1HIGHmedium confidence
EG Risk
48
EG Risk 48/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity71% × 45%
Impact severity (EG Severity): CVSS 7.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
44th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.1): severity, escalated by confirmed exploitation. This CVE's 7.1 is its impact severity (EG Severity), not escalated.

EG Severity
7.1 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 15, 2026

Last Modified

September 30, 2026

Advisory Details (2)

Auto-updated Sep 15, 2026
Patch available. Sources: github, github_commit.
GitHub commit Patch Available

commit 6bf9c3a9cb66 (gouef/githubtoplanguages)

Patch available: gouef/githubtoplanguages v1.1.4 (contains commit 6bf9c3a9cb66)

https://github.com/gouef/githubtoplanguages/commit/6bf9c3a9cb66c937b9047ca266b3d02f2bb11027
GitHub advisoryMentions a patch (unverified)

githubtoplanguages: Command Injection via Issue Title in Discord Notification Workflow · Advisory · gouef/githubtoplanguages · GitHub

https://github.com/gouef/githubtoplanguages/security/advisories/GHSA-c3xh-98xp-6qhf

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 47× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  2. 2026-10-31 18:48 UTCEG score recompute
  3. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  4. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  5. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  6. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  7. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  8. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  9. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  10. 2026-10-25 14:16 UTCEG score recompute
  11. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  12. 2026-10-24 03:57 UTCEG score recompute
  13. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  14. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  15. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  16. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  17. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  18. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  19. 2026-10-18 03:27 UTCEG score recompute
  20. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  21. 2026-10-16 16:43 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  22. 2026-10-16 13:02 UTCEG score recompute
  23. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  24. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  25. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
Show 57 more
  1. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  2. 2026-10-12 15:53 UTCEG score recompute
  3. 2026-10-11 19:29 UTCEG score recompute
  4. 2026-10-11 16:51 UTCEG score recompute
  5. 2026-10-11 14:14 UTCEG score recompute
  6. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  7. 2026-10-11 06:27 UTCEG score recompute
  8. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  9. 2026-10-10 04:50 UTCEG score recompute
  10. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  11. 2026-10-08 22:16 UTCEG score recompute
  12. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  13. 2026-10-08 07:35 UTCEG score recompute
  14. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  15. 2026-10-07 03:45 UTCEG score recompute
  16. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  17. 2026-10-06 02:18 UTCEG score recompute
  18. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  19. 2026-10-05 00:28 UTCEG score recompute
  20. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  21. 2026-10-03 22:47 UTCEG score recompute
  22. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  23. 2026-10-02 21:00 UTCEG score recompute
  24. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  25. 2026-10-02 08:17 UTCEG score recompute
  26. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  27. 2026-09-30 18:09 UTCEG score recompute
  28. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  29. 2026-09-30 01:08 UTCEG score recompute
  30. 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  31. 2026-09-29 09:56 UTCEG score recompute
  32. 2026-09-28 21:14 UTCEG score recompute
  33. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  34. 2026-09-27 19:47 UTCEG score recompute
  35. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  36. 2026-09-26 18:21 UTCEG score recompute
  37. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  38. 2026-09-26 05:35 UTCEG score recompute
  39. 2026-09-24 15:26 UTCEG score recompute
  40. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  41. 2026-09-24 02:43 UTCEG score recompute
  42. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  43. 2026-09-23 01:16 UTCEG score recompute
  44. 2026-09-21 23:50 UTCEG score recompute
  45. 2026-09-20 22:25 UTCEG score recompute
  46. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  47. 2026-09-19 20:59 UTCEG score recompute
  48. 2026-09-18 19:34 UTCEG score recompute
  49. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  50. 2026-09-18 06:51 UTCEG score recompute
  51. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  52. 2026-09-17 18:08 UTCEG score recompute
  53. 2026-09-16 19:59 UTCEG score recompute
  54. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  55. 2026-09-15 18:32 UTCEG score recompute
  56. 2026-09-15 17:44 UTCEG score recomputeFirst assessed: 7.1 HIGH
  57. 2026-09-15 17:43 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-58502?
CVE-2026-58502 is a high-severity vulnerability; its CVE record was published on September 15, 2026. githubtoplanguages generates a user's top GitHub languages as an SVG. The .github/workflows/discord-issue.yml workflow runs when an issue is opened or closed and interpolates github.event.issue.title directly into the Bash assignment for ISSUE_TITLE before shell parsing. An issue title containing…
When was the CVE record for CVE-2026-58502 published?
The CVE record for CVE-2026-58502 was published on September 15, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 30, 2026; the record at its source may have been updated since.
Is CVE-2026-58502 actively exploited?
CVE-2026-58502 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (44th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-58502?
CVE-2026-58502 has a CVSS base score of 7.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-58502?
A fix for CVE-2026-58502 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-58502

Explore →

Is Your Infrastructure Affected by CVE-2026-58502?

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

Book a Demo →Browse All CVEs