CVE-2026-34243: wenxian GitHub Actions RCE Vulnerability

CVE-2026-34243 Overview

CVE-2026-34243 is a command injection vulnerability in wenxian, a tool used to generate BIBTEX files from given identifiers (DOI, PMID, arXiv ID, or paper title). In versions 0.3.1 and prior, a GitHub Actions workflow uses untrusted user input from issue_comment.body directly inside a shell command, allowing potential command injection and arbitrary code execution on the runner.

Critical Impact

Attackers can execute arbitrary commands on GitHub Actions runners by crafting malicious issue comments, potentially compromising CI/CD pipelines, stealing secrets, and gaining unauthorized access to repository resources.

Affected Products

• wenxian versions 0.3.1 and prior

Discovery Timeline

• 2026-03-31 - CVE CVE-2026-34243 published to NVD
• 2026-04-01 - Last updated in NVD database

Technical Details for CVE-2026-34243

Vulnerability Analysis

This vulnerability falls under CWE-77 (Improper Neutralization of Special Elements used in a Command), commonly known as Command Injection. The wenxian project contains a GitHub Actions workflow that processes issue comments without proper input sanitization. When a user submits a comment on an issue, the workflow extracts the comment body and incorporates it directly into a shell command without escaping or validation.

GitHub Actions workflows that use issue_comment events are particularly susceptible to this type of attack because issue comments can be submitted by any GitHub user, including unauthenticated users on public repositories. The lack of input validation means that shell metacharacters and command sequences embedded in the comment body are interpreted by the shell, enabling attackers to break out of the intended command context.

Root Cause

The root cause of this vulnerability is the direct interpolation of untrusted user input (issue_comment.body) into a shell command within a GitHub Actions workflow. The workflow fails to sanitize, escape, or validate the input before using it in a command execution context. This pattern is a classic command injection vulnerability where user-controlled data crosses a trust boundary into a privileged execution environment.

Attack Vector

An attacker can exploit this vulnerability remotely by submitting a specially crafted comment on an issue in the affected repository. The attack requires no authentication beyond a standard GitHub account and can be executed with low complexity. The malicious payload embedded in the comment could include shell command sequences such as command substitution ($(...) or backticks), command separators (;, &&, ||), or other shell metacharacters that allow arbitrary command execution.

Upon successful exploitation, the attacker gains the ability to execute commands with the permissions of the GitHub Actions runner, which typically includes access to repository secrets, GitHub tokens, and the ability to modify repository content. For more technical details, refer to the GitHub Security Advisory.

Detection Methods for CVE-2026-34243

Indicators of Compromise

• Unusual or suspicious comments on repository issues containing shell metacharacters or command sequences
• Unexpected workflow runs triggered by issue_comment events
• Anomalous network connections or data exfiltration attempts originating from GitHub Actions runners
• Unauthorized modifications to repository secrets or workflow files

Detection Strategies

• Review GitHub Actions workflow logs for unexpected command outputs or error messages
• Monitor repository audit logs for suspicious issue_comment activity
• Implement code scanning to identify workflows that directly use untrusted event payloads in shell commands
• Use GitHub's built-in secret scanning to detect potential credential exposure

Monitoring Recommendations

• Enable GitHub Actions workflow run notifications for security review
• Set up alerts for workflow failures or unexpected behavior patterns
• Implement regular audits of GitHub Actions workflows for insecure patterns
• Monitor repository access logs for unauthorized token usage

How to Mitigate CVE-2026-34243

Immediate Actions Required

• Disable or restrict the vulnerable GitHub Actions workflow until a patch is available
• Review repository for signs of exploitation, including unexpected workflow runs or unauthorized changes
• Rotate any secrets or tokens that may have been exposed through the CI/CD pipeline
• Restrict who can comment on issues if using a public repository

Patch Information

At time of publication, there are no publicly available patches for this vulnerability. Organizations using wenxian should monitor the GitHub Security Advisory for updates regarding official fixes.

Workarounds

• Disable the affected workflow by removing or commenting out the issue_comment trigger
• Implement input validation using an intermediate action that sanitizes comment content before processing
• Use actions/github-script or environment variables with proper escaping instead of direct shell interpolation
• Restrict workflow permissions using the permissions key to minimize potential impact
• Consider using pull_request_target event restrictions and manual approval workflows for sensitive operations

# Example: Disable vulnerable workflow temporarily
# In .github/workflows/vulnerable-workflow.yml, comment out the trigger:
# on:
#   issue_comment:
#     types: [created]

# Alternative: Add environment variable escaping
env:
  COMMENT_BODY: ${{ github.event.comment.body }}
# Then use proper quoting in shell commands
run: |
  # Use environment variable with proper quoting
  echo "Processing comment safely"