CVE-2026-34243

wenxian: Command Injection in GitHub Actions Workflow via issue_comment.body

• Remote attackers can inject arbitrary shell commands via issue comments

• Potential impacts:

  • Execution of arbitrary commands in GitHub Actions runner
  • Access to GITHUB_TOKEN
  • Exfiltration of repository data
  • CI/CD pipeline compromise

This issue affects all current versions of the repository as the vulnerable workflow is present in the main branch.

The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths. Typical impact: varies by context: data corruption, logic bypass, or denial of service.

CVE-2026-34243 has a CVSS score of 9.8 (Critical). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. No fixed version is listed yet, so configuration controls and monitoring matter more in the interim.

Kodem intelligence

Avoid directly interpolating untrusted user input into shell commands.

Instead, pass github.event.comment.body through an environment variable and reference it safely within the script:

- name: Extract identifiers
  id: extract-identifiers
  env:
    COMMENT_BODY: ${{ github.event.comment.body }}
  run: |
    identifiers=$(echo "$COMMENT_BODY" | grep -oE '@njzjz-bot .*' | head -n1 | cut -c12- | xargs)
    echo "identifiers=$identifiers" >> $GITHUB_OUTPUT

1. What is CVE-2026-34243? CVE-2026-34243 is a critical-severity improper input validation vulnerability in njzjz/wenxian (actions), affecting versions <= 0.3.1. No fixed version is listed yet. The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths.
2. How severe is CVE-2026-34243? CVE-2026-34243 has a CVSS score of 9.8 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of njzjz/wenxian are affected by CVE-2026-34243? njzjz/wenxian (actions) versions <= 0.3.1 is affected.
4. Is there a fix for CVE-2026-34243? No fixed version is listed for CVE-2026-34243 yet. Monitor the advisory for updates and apply mitigations in the interim.
5. Is CVE-2026-34243 exploitable, and should I be worried? Whether CVE-2026-34243 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-34243 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-34243? No fixed version is listed yet. In the interim: Validate all external input against an allowlist of expected values, types, and ranges before processing.