CVE-2026-34243
Command Injection in wenxian GitHub Actions Allows Code Execution
Publication date: 2026-03-31
Last updated on: 2026-04-03
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| njzjz | wenxian | to 0.3.1 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-77 | The product constructs all or part of a command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended command when it is sent to a downstream component. |
| CWE-78 | The product constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command when it is sent to a downstream component. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2026-34243 is a critical command injection vulnerability in the GitHub Actions workflow of the wenxian tool repository. The workflow processes user input from issue comments without proper sanitization, directly inserting this input into shell commands. This allows an attacker to inject and execute arbitrary shell commands on the GitHub Actions runner.
Specifically, the vulnerability arises because the content of issue_comment.body is interpolated directly into a shell command, enabling malicious input to break out of the intended command context. For example, an attacker can post a specially crafted comment that executes commands like 'whoami' on the runner, with the output visible in workflow logs.
The root cause is improper neutralization of special elements used in commands (CWE-77), where untrusted input is not safely handled before execution.
How can this vulnerability impact me? :
This vulnerability allows remote attackers to execute arbitrary commands on the GitHub Actions runner without any privileges or user interaction.
- Remote arbitrary command execution on the CI/CD runner.
- Potential access to the GITHUB_TOKEN, which can be used to access repository data and perform actions on behalf of the repository.
- Exfiltration of sensitive repository data.
- Compromise of the CI/CD pipeline, potentially affecting the integrity and availability of builds and deployments.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by examining the GitHub Actions workflow logs for evidence of command injection attempts. Specifically, look for unusual commands executed in the workflow triggered by issue comments, such as injected shell commands appearing in the logs.
A proof-of-concept involves posting a comment like '@njzjz-bot paper123" ) ; whoami ; #' which results in execution of the injected 'whoami' command on the runner, with output visible in the workflow logs.
To detect exploitation attempts, you can search the workflow logs for suspicious patterns or commands injected via issue comments.
- Check GitHub Actions workflow logs for commands executed from issue_comment.body input.
- Look for unusual shell commands or output in the logs that do not correspond to expected workflow behavior.
- Use grep or similar tools to search logs for keywords like 'whoami', 'id', or other shell commands that might indicate injection.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation involves modifying the GitHub Actions workflow to avoid direct interpolation of untrusted user input into shell commands.
Instead of inserting 'github.event.comment.body' directly into shell commands, pass it as an environment variable and safely reference it within the script.
For example, update the workflow step to:
- Use an environment variable COMMENT_BODY to hold the user input.
- Extract identifiers safely using a command like: identifiers=$(echo "$COMMENT_BODY" | grep -oE '@njzjz-bot .*' | head -n1 | cut -c12- | xargs)
- Echo the sanitized identifiers to $GITHUB_OUTPUT.
Since no patches are publicly available at the time of publication, this workaround is the recommended immediate step to prevent command injection.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows remote arbitrary command execution on the GitHub Actions runner, which can lead to unauthorized access to the GITHUB_TOKEN, exfiltration of repository data, and compromise of the CI/CD pipeline.
Such unauthorized access and data exfiltration could potentially lead to violations of data protection regulations and standards like GDPR and HIPAA, which require strict controls over data confidentiality, integrity, and availability.
Because the vulnerability impacts confidentiality, integrity, and availability at a high level, organizations using the affected software without mitigation may face compliance risks related to protecting sensitive data and maintaining secure development environments.