ZeroDay Findings
Sign inSign up

Findings

CVE-2025-54416

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

Published Jul 25, 2025 · corrected/updated Sep 10, 2026 · evidence confidence high

#### **Overview** A critical vulnerability has been identified in the 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 pattern within the action's codebase. Although initial sanitization using properly escapes untrusted input, subsequent unescaping via 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. #### **Proof-of-Concept (PoC)** 1. Create a branch with the name . 2. Trigger the vulnerable workflow by opening a pull request into the target repository. 3. Observe arbitrary code execution in the workflow logs. Example output: #### **Impact** This vulnerability enables arbitrary command execution in repositories consuming outputs from . The severity of the impact depends on the permissions granted to the and the context of the triggering event. Potential consequences include: - Theft of sensitive secrets stored in the repository. - Unauthorized write access to the repository. - Compromise of the repository's integrity and security. #### **Mitigation and Resolution** To address this vulnerability, the unsafe pattern must be replaced with safer alternatives. Specifically, direct calls can achieve the same functionality without unescaping shell-unsafe characters. Below is the recommended fix: This approach ensures that all outputs remain properly escaped and safe for downstream consumption. #### **Recommendations** 1. **Immediate Action**: Develo

Grounded briefings

Catalog interpretations for three audiences. Each brief cites ingested metadata and the original advisories below. They are not independent research and they do not invent exploit steps.

Executive

CVE-2025-54416 is a critical public vulnerability record for this product. It is not currently listed in the CISA Known Exploited catalog. Check the linked vendor or CERT advisories for patch status. This summary is a catalog interpretation of the ingested metadata and cites the original advisories below.

System administrator

Identify whether this product is in your estate, then compare installed versions with the affected ranges. Affected packages or ranges on record: tj-actions/branch-names (0 → 9.0.0). Check the linked vendor or CERT advisories for patch status. Prefer the vendor or distribution advisory linked in Sources before changing production systems. This is a catalog interpretation, not a runbook.

Security analyst

Signals on file: CVSS 9.1, EPSS 0.7%. It is not currently listed in the CISA Known Exploited catalog. Weakness classes: CWE-77. Sources contributing to this record: cve_org, epss, github, osv. Public exploit references, when present, are outbound links only and are not proof of active exploitation. This is a catalog interpretation of stored metadata.

Exploitation and remediation

  • Exploitation evidence

    Not listed as known exploited in CISA KEV. Not in the CISA KEV catalog.

  • Patch and remediation

    No required-action text is stored yet. Use the vendor or CERT links in Sources for patch availability.

  • Safe detection guidance

    Compare installed versions with the affected ranges below and verify the advisory from the original publisher. This site stores metadata and outbound links only; it does not ship exploit code or proof-of-concept payloads.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Jul 25, 2025 · GitHub Advisory Database

    Detected

    #### **Overview** A critical vulnerability has been identified in the 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 rema

  2. Sep 10, 2026 · GitHub Advisory Database

    Fix available

    tj-actions/branch-names fixed in 9.0.0

  3. Sep 10, 2026 · GitHub Advisory Database

    Fix available

    tj-actions/branch-names fixed in 9.0.0

  4. Sep 10, 2026 · GitHub Advisory Database

    Updated

    #### **Overview** A critical vulnerability has been identified in the 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 rema

Affected

  • GitHub Actions tj-actions/branch-names0 → 9.0.0

Sources

References