CVE-2025-31479

HIGHNVD 8.28.2
EchelonGraph scoreMEDIUM confidence

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

Score 8.2 from GitHub Security Advisory (severity: HIGH) published 2025-04-02. NVD baseline CVSS 8.2; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this week

Also known asEUVD-2025-9624 (ENISA EUVD) · GHSA-26wh-cc3r-w6pj (GitHub Security Advisories)Source: ENISA EUVD

8.2EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 8.2Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

canonical/get-workflow-version-action is a GitHub composite action to get commit SHA that GitHub Actions reusable workflow was called with. Prior to 1.0.1, if the get-workflow-version-action step fails, the exception output may include the GITHUB_TOKEN. If the full token is included in the exception output, GitHub will automatically redact the secret from the GitHub Actions logs. However, the token may be truncated—causing part of the GITHUB_TOKEN to be displayed in plaintext in the GitHub Actions logs. Anyone with read access to the GitHub repository can view GitHub Actions logs. For public repositories, anyone can view the GitHub Actions logs. The opportunity to exploit this vulnerability is limited—the GITHUB_TOKEN is automatically revoked when the job completes. However, there is an opportunity for an attack in the time between the GITHUB_TOKEN being displayed in the logs and the completion of the job. Users using the github-token input are impacted. This vulnerability is fixed in 1.0.1.

CVSS v3
8.2
EG Score
8.2HIGHmedium confidence
EG Risk
37
EG Risk 37/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)
Severity82% × 45%
Impact severity (EG Severity): CVSS 8.2 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.6% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (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.
EPSS PROB
0.6%
EPSS %ILE
48th
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 (8.2): severity, escalated by confirmed exploitation. This CVE's 8.2 is its impact severity (EG Severity), not escalated.

EG Severity
8.2 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.6% 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 or medium mission impact; Track* at high (mission-essential systems).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 or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (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

April 2, 2025

Last Modified

April 15, 2026

Advisory Details (3)

Auto-updated Sep 9, 2026
Patch available. Sources: github_commit, github.
GitHub advisoryMentions a patch (unverified)

Partial leak of GITHUB_TOKEN in exception output · Advisory · canonical/get-workflow-version-action · GitHub

https://github.com/canonical/get-workflow-version-action/security/advisories/GHSA-26wh-cc3r-w6pj
Web page

Github token secret partially displayed when error occurs · Issue #2 · canonical/get-workflow-version-action · GitHub

https://github.com/canonical/get-workflow-version-action/issues/2
GitHub commit Patch Available

commit 88281a62e96e (canonical/get-workflow-version-action)

Patch available: canonical/get-workflow-version-action v1.0.1 (contains commit 88281a62e96e)

https://github.com/canonical/get-workflow-version-action/commit/88281a62e96e1c0ef4df30352ae0668a9f3e3369

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
actionscanonical/get-workflow-version-action @ 1.0.1 (fixes < 1.0.1)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 41× 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.

Showing the most recent 96 of 229 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 4 repeat rows among the latest 100 are merged into the row they repeat. The 133 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 16:42 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  2. 2026-11-01 16:32 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  3. 2026-11-01 08:07 UTCEG score recompute
  4. 2026-11-01 08:07 UTCGHSA enrichmentGHSA-26wh-cc3r-w6pj · GitHub severity HIGH · GitHub CVSS 8.2
  5. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  6. 2026-10-30 16:32 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  7. 2026-10-29 16:31 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  8. 2026-10-28 16:30 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  9. 2026-10-27 16:30 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  10. 2026-10-27 11:12 UTCEG score recompute
  11. 2026-10-26 16:29 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  12. 2026-10-25 16:35 UTCEG score recompute
  13. 2026-10-25 16:31 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  14. 2026-10-24 16:31 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  15. 2026-10-23 16:30 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  16. 2026-10-22 16:32 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  17. 2026-10-21 16:31 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  18. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  19. 2026-10-19 16:30 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  20. 2026-10-18 17:59 UTCEG score recompute
  21. 2026-10-18 16:30 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  22. 2026-10-18 05:39 UTCEG score recompute
  23. 2026-10-17 16:32 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  24. 2026-10-16 16:38 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  25. 2026-10-15 16:30 UTCEPSS rescoreEPSS 0.6% · 46th percentile
Show 71 more
  1. 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  2. 2026-10-13 16:32 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  3. 2026-10-12 17:11 UTCEG score recompute
  4. 2026-10-12 16:32 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  5. 2026-10-11 20:43 UTCEG score recompute
  6. 2026-10-11 18:54 UTCEG score recompute
  7. 2026-10-11 15:32 UTCEG score recompute
  8. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  9. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  10. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  11. 2026-10-08 17:09 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  12. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  13. 2026-10-06 21:44 UTCOSV refresh
  14. 2026-10-06 15:16 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  15. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  16. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  17. 2026-10-03 14:24 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  18. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  19. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  20. 2026-09-29 15:19 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  21. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  22. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  23. 2026-09-26 00:24 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  24. 2026-09-24 14:02 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  25. 2026-09-23 13:47 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  26. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  27. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  28. 2026-09-17 03:20 UTCOSV refresh
  29. 2026-09-16 14:07 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  30. 2026-09-16 05:13 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  31. 2026-09-13 16:46 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  32. 2026-09-12 15:00 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  33. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  34. 2026-09-11 09:35 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  35. 2026-09-10 09:33 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  36. 2026-09-08 21:59 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  37. 2026-09-07 16:00 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  38. 2026-09-06 13:46 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  39. 2026-09-04 05:05 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  40. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  41. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  42. 2026-08-30 19:16 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  43. 2026-08-30 01:21 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  44. 2026-08-29 03:43 UTCOSV refresh
  45. 2026-08-28 21:40 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  46. 2026-08-27 14:24 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  47. 2026-08-26 14:45 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  48. 2026-08-25 13:48 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  49. 2026-08-24 14:16 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  50. 2026-08-23 00:18 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  51. 2026-08-21 23:48 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  52. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  53. 2026-08-18 13:47 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  54. 2026-08-17 13:46 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  55. 2026-08-16 14:55 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  56. 2026-08-16 02:13 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  57. 2026-08-15 01:29 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  58. 2026-08-13 21:59 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  59. 2026-08-12 15:20 UTCOSV refresh
  60. 2026-08-12 13:50 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  61. 2026-08-10 23:59 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  62. 2026-08-09 13:45 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  63. 2026-08-07 16:26 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  64. 2026-08-06 13:46 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  65. 2026-08-05 19:16 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  66. 2026-08-04 15:09 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  67. 2026-08-04 10:37 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  68. 2026-08-03 10:35 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  69. 2026-08-02 02:26 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  70. 2026-08-01 04:15 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  71. 2026-07-30 16:27 UTCEPSS rescoreEPSS 0.6% · 44th percentile

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2025-31479?
CVE-2025-31479 is a high-severity vulnerability; its CVE record was published on April 2, 2025. canonical/get-workflow-version-action is a GitHub composite action to get commit SHA that GitHub Actions reusable workflow was called with. Prior to 1.0.1, if the get-workflow-version-action step fails, the exception output may include the GITHUB_TOKEN. If the full token is included in the…
When was the CVE record for CVE-2025-31479 published?
The CVE record for CVE-2025-31479 was published on April 2, 2025. 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 April 15, 2026; the record at its source may have been updated since.
Is CVE-2025-31479 actively exploited?
CVE-2025-31479 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (48th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-31479?
CVE-2025-31479 has a CVSS v3 base score of 8.2 (NVD).
How do I remediate CVE-2025-31479?
A fix for CVE-2025-31479 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-2025-31479

Explore →

Is Your Infrastructure Affected by CVE-2025-31479?

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

Book a Demo →Browse All CVEs