Attack Chain

1. An attacker submits a malicious comment to a GitHub issue in the affected repository, crafted to exploit the command injection vulnerability.
2. The comment contains a payload designed to break out of the intended command context and inject arbitrary shell commands.
3. The GitHub Actions workflow is triggered by the issue_comment event.
4. The workflow executes the vulnerable step, which interpolates the attacker-controlled github.event.comment.body into a shell command. Specifically, the command echo identifiers=$(echo "${{ github.event.comment.body }}" | grep -oE '@njzjz-bot .*' | head -n1 | cut -c12- | xargs) >> $GITHUB_OUTPUT is executed.
5. The attacker's injected commands are executed on the GitHub Actions runner with the privileges of the runner environment.
6. The attacker could leverage access to the GITHUB_TOKEN to interact with the repository, potentially exfiltrating data or modifying code.
7. The attacker can use the injected commands to compromise the CI/CD pipeline.
8. The final objective is arbitrary code execution on the runner, data exfiltration, or CI/CD pipeline compromise.

Impact

This vulnerability allows remote attackers to inject arbitrary shell commands into the GitHub Actions runner by posting malicious comments on issues. Successful exploitation can lead to the execution of arbitrary code within the runner environment. This could provide attackers with access to sensitive information, including the GITHUB_TOKEN, allowing them to exfiltrate repository data or modify code. The compromise of the CI/CD pipeline can lead to supply chain attacks and other severe consequences. The actions/njzjz/wenxian repository (vulnerable: <= 0.3.1) is affected by this vulnerability.

Recommendation

• Deploy the "Detect GitHub Actions Command Injection via Issue Comments" Sigma rule to detect exploitation attempts by monitoring process creation events with suspicious command line arguments.
• Implement the suggested fix provided in the advisory by passing github.event.comment.body through an environment variable and referencing it safely within the script to mitigate the command injection vulnerability.
• Audit all GitHub Actions workflows for similar vulnerabilities where untrusted user input is directly interpolated into shell commands, and apply proper sanitization techniques.
• Patch actions/njzjz/wenxian to a version greater than 0.3.1 to remediate CVE-2026-34243.