tj-actions/branch-names has a Command Injection Vulnerability

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

9.1 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:L

EPSS

• CVE-2025-54416: 0.68% estimated exploitation activity in the next 30 days; percentile 52.34 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Overview 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. Technical Details The vulnerability stems from the unsafe use of the eval printf "%s" pattern within the action's codebase. Although initial sanitization using printf "%q" properly escapes untrusted input, subsequent unescaping via eval printf "%s" reintroduces command injection risks. This unsafe pattern is demonstrated in the following code snippet: This approach allows attackers to inject arbitrary commands into workflows consuming these outputs, as shown in the Proof-of-Concept (PoC) below.…

Published by the source

25 Jul 2025, 19:28 UTC

Last modified by the source

28 Jul 2025, 13:00 UTC

Source last checked

26 Oct 2026, 17:08 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-gq52-6phf-x2r6

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-54416

Advisory: tj-actions/branch-names has a Command Injection Vulnerability
IDs: CVE-2025-54416, GHSA-gq52-6phf-x2r6
Record: https://patchnext.com/advisories/cve-2025-54416 (revision 1, source checked 26 Oct 2026, 17:08 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: tj-actions/branch-names 9.0.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- GitHub Actions tj-actions/branch-names: affected <= 8.2.1; fixed in 9.0.0

## Suggested inspection (read-only)
- GitHub Actions tj-actions/branch-names: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on tj-actions/branch-names.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-gq52-6phf-x2r6 (GitHub-reviewed advisory GHSA-gq52-6phf-x2r6 lists affected ranges: GitHub Actions tj-actions/branch-names >=0 <=8.2.1)

Commands are suggestions: review each one before running it.