CVE-2025-54416

CRITICALNVD 9.19.1—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.1 under NVD CVSS v3. EPSS exploit probability: 0.6%, top 57% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Trending — 3 sources updated this weekElevated
9.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.1Exploit: Elevated riskExposed: 0

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

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.1(medium)
EG Risk
57(Track)
EG Risk 57/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
Severity91% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
43%
KEV
Not listed

Published

July 26, 2025

Last Modified

April 15, 2026

Advisory Details (3)

Auto-updated May 21, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

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
generic

Release v9.0.0 · tj-actions/branch-names · GitHub

https://github.com/tj-actions/branch-names/releases/tag/v9.0.0
generic

security: fix unsafe outputs (#420) · tj-actions/branch-names@e497ceb · GitHub

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

Weakness Classification(1)

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

Data Freshness Timeline

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

Showing the most recent 100 of 126 total refreshes for this CVE.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2025-54416?
CVE-2025-54416 is a critical vulnerability 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 CVE-2025-54416 disclosed?
CVE-2025-54416 was first published in the National Vulnerability Database on July 26, 2025, with the most recent update on April 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-54416 actively exploited?
CVE-2025-54416 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 57.1% of all 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?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-54416, 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-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.

Start Free Scan →Browse All CVEs