CVE-2025-54416

CRITICALNVD 9.19.1
EchelonGraph scoreMEDIUM confidence

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

Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2025-07-25. NVD baseline CVSS 9.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Elevated

Also known asEUVD-2025-22774 (ENISA EUVD) · GHSA-gq52-6phf-x2r6 (GitHub Security Advisories)Source: ENISA EUVD

9.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (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.7%CVSS: 9.1Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

tj-actions/branch-names is a Github actions repository that contains workflows to retrieve branch or tag names with support for all events. In versions 8.2.1 and below, a critical vulnerability has been identified in the tj-actions/branch-names' GitHub Action workflow which allows arbitrary command execution in downstream workflows. This issue arises due to inconsistent input sanitization and unescaped output, enabling malicious actors to exploit specially crafted branch names or tags. While internal sanitization mechanisms have been implemented, the action outputs remain vulnerable, exposing consuming workflows to significant security risks. This is fixed in version 9.0.0

CVSS v3
9.1
EG Score
9.1CRITICALmedium confidence
EG Risk
57
EG Risk 57/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)
Severity91% × 45%
Impact severity (EG Severity): CVSS 9.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 or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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.7%
EPSS %ILE
52nd
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 (9.1): severity, escalated by confirmed exploitation. This CVE's 9.1 is its impact severity (EG Severity), not escalated.

EG Severity
9.1 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.7% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). 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: 60 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 public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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)60 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 partial (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

July 26, 2025

Last Modified

April 15, 2026

Advisory Details (3)

Auto-updated Aug 1, 2026
Patch available. Sources: github_commit, github_release, github.
GitHub advisoryMentions a patch (unverified)

Command Injection Vulnerability in tj-actions/branch-names · Advisory · tj-actions/branch-names · GitHub

https://github.com/tj-actions/branch-names/security/advisories/GHSA-gq52-6phf-x2r6
GitHub release Patch Available

v9.0.0

Patch available: tj-actions/branch-names v9.0.0

https://github.com/tj-actions/branch-names/releases/tag/v9.0.0
GitHub commit Patch Available

commit e497ceb8ccd4 (tj-actions/branch-names)

Patch available: tj-actions/branch-names v9.0.0 (contains commit e497ceb8ccd4)

https://github.com/tj-actions/branch-names/commit/e497ceb8ccd43fd9573cf2e375216625bc411d1f

Vendor Advisories for CVE-2025-54416(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
actionstj-actions/branch-names @ 9.0.0 (fixes <= 8.2.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 14× in last 7d / 45× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 288 rows on record for this CVE, as 98 entries (2 repeats merged).

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. 2 repeat rows among the latest 100 are merged into the row they repeat. The 188 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2025-54416?
CVE-2025-54416 is a critical-severity vulnerability; its CVE record was published on July 26, 2025. tj-actions/branch-names is a Github actions repository that contains workflows to retrieve branch or tag names with support for all events. In versions 8.2.1 and below, a critical vulnerability has been identified in the tj-actions/branch-names' GitHub Action workflow which allows arbitrary command…
When was the CVE record for CVE-2025-54416 published?
The CVE record for CVE-2025-54416 was published on July 26, 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-54416 actively exploited?
CVE-2025-54416 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (52nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-54416?
CVE-2025-54416 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2025-54416?
A fix for CVE-2025-54416 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-54416 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2025-54416

Explore →

Is Your Infrastructure Affected by CVE-2025-54416?

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

Book a Demo →Browse All CVEs