CVE-2026-34243: wenxian Command Injection Vulnerability

CRITICAL
Advisory Identifier: GHSA-r4fj-r33x-8v88
CVSS 9.8
CWE-78 CWE-20 CWE-77
Published
Advisory Summary

CVE-2026-34243 is a CRITICAL (CVSS 9.8) command injection vulnerability (CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')) affecting wenxian libraries in the GitHub Actions ecosystem. The issue involves command injection in github actions workflow via `issue_comment.body`. Remediation is available in the latest vendor maintenance releases.

CVE-2026-34243 at a Glance

CVE Identifier CVE-2026-34243
GHSA Identifier GHSA-r4fj-r33x-8v88
Severity CRITICAL
CVSS v3.1 Base Score 9.8
CWE Classification CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')
Affected Product wenxian
Package Ecosystem GitHub Actions
Published Date
Last Updated

Security Impact

CVSS: 9.8

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity High (I:H)
Availability High (A:H)

How to Fix CVE-2026-34243

To remediate this vulnerability, upgrade all affected wenxian dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

njzjz/wenxian fixed: Latest secure release
Upgrade njzjz/wenxian to Latest secure release
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for njzjz/wenxian

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-34243, inspect your project dependencies for wenxian:

inspect dependencies for njzjz/wenxian

Analyze the terminal output to locate any version of wenxian in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection'), where 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. In wenxian, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

#### Summary 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. #### Details The workflow is triggered by `issue_comment`, which can be controlled by external users. In the following step: ```bash echo identifiers=$(echo "${{ github.event.comment.body }}" | grep -oE '@njzjz-bot .*' | head -n1 | cut -c12- | xargs) >> $GITHUB_OUTPUT ``` the value of `github.event.comment.body` is directly interpolated into a shell command inside `run:`. Since GitHub Actions evaluates `${{ }}` before execution, attacker-controlled input is injected into the shell context without sanitization. This creates a command injection risk. Additionally, the extracted value is later reused in another step that constructs output using backticks: ```bash echo '@${{ github.event.comment.user.login }} Here is the BibTeX entry for `${{ steps.extract-identifiers.outputs.identifiers }}`:' ``` which may further propagate unsafe content. #### PoC 1. Go to an issue in the repository 2. Post a comment such as: `@njzjz-bot paper123" ) ; whoami ; # ` 3. Observe whether the command is executed or reflected in logs/output <img width="658" height="203" alt="poc" src="https://github.com/user-attachments/assets/084ac264-8cb9-4721-8279-26a1da9b891f" /> The injected payload successfully breaks out of the quoted context and executes arbitrary shell commands. As shown in the workflow logs, the injected `whoami` command is executed, and the output (`runner`) is printed. This confirms that attacker-controlled input from `github.event.comment.body` is interpreted as shell commands. This demonstrates a clear command injection vulnerability in the workflow. #### Impact * 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. ### Suggested Fix 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: ```yaml - 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

CVE-2026-34243 Affected wenxian Versions

1 component(s)
Product / Package Ecosystem Affected Versions Fixed Version
njzjz/wenxian
GitHub Actions
≤ 0.3.1

References

Frequently Asked Questions

What is CVE-2026-34243?
CVE-2026-34243 is a security vulnerability in wenxian involving Command Injection in GitHub Actions Workflow via `issue_comment.body` under CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection').
Which wenxian versions are affected?
Affected versions include releases prior to current release patches across affected packages: njzjz/wenxian.
What version fixes CVE-2026-34243?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
Is njzjz/wenxian affected?
Yes, njzjz/wenxian is affected in releases prior to Latest secure release. Upgrade your dependency to Latest secure release or later.
What is the CVSS score of CVE-2026-34243?
CVE-2026-34243 has a CVSS v3.1 base score of 9.8 (CRITICAL) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.
What CWE is associated with CVE-2026-34243?
CVE-2026-34243 is classified under CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') (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.).
How can I check GitHub Actions dependencies for CVE-2026-34243?
Run the dependency tree command: 'inspect dependencies for njzjz/wenxian'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-r4fj-r33x-8v88",
  "modified" : "2026-03-31T18:54:46Z",
  "published" : "2026-03-29T15:39:56Z",
  "aliases" : [ "CVE-2026-34243" ],
  "summary" : "wenxian: Command Injection in GitHub Actions Workflow via `issue_comment.body` ",
  "details" : "#### Summary\n\nA 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.\n\n#### Details\n\nThe workflow is triggered by `issue_comment`, which can be controlled by external users.\nIn the following step:\n\n```bash\necho identifiers=$(echo \"${{ github.event.comment.body }}\" | grep -oE '@njzjz-bot .*' | head -n1 | cut -c12- | xargs) >> $GITHUB_OUTPUT\n```\n\nthe value of `github.event.comment.body` is directly interpolated into a shell command inside `run:`.\n\nSince GitHub Actions evaluates `${{ }}` before execution, attacker-controlled input is injected into the shell context without sanitization. This creates a command injection risk.\n\nAdditionally, the extracted value is later reused in another step that constructs output using backticks:\n\n```bash\necho '@${{ github.event.comment.user.login }} Here is the BibTeX entry for `${{ steps.extract-identifiers.outputs.identifiers }}`:'\n```\n\nwhich may further propagate unsafe content.\n\n#### PoC\n\n1. Go to an issue in the repository\n2. Post a comment such as:\n\n`@njzjz-bot paper123\" ) ; whoami ; #\n`\n\n3. Observe whether the command is executed or reflected in logs/output\n<img width=\"658\" height=\"203\" alt=\"poc\" src=\"https://github.com/user-attachments/assets/084ac264-8cb9-4721-8279-26a1da9b891f\" />\n\nThe injected payload successfully breaks out of the quoted context and executes arbitrary shell commands.\n\nAs shown in the workflow logs, the injected `whoami` command is executed, and the output (`runner`) is printed. This confirms that attacker-controlled input from `github.event.comment.body` is interpreted as shell commands.\n\nThis demonstrates a clear command injection vulnerability in the workflow.\n\n#### Impact\n\n* Remote attackers can inject arbitrary shell commands via issue comments\n* Potential impacts:\n\n  * Execution of arbitrary commands in GitHub Actions runner\n  * Access to `GITHUB_TOKEN`\n  * Exfiltration of repository data\n  * CI/CD pipeline compromise\n\n\nThis issue affects all current versions of the repository as the vulnerable workflow is present in the main branch.\n\n### Suggested Fix\n\nAvoid directly interpolating untrusted user input into shell commands.\n\nInstead, pass `github.event.comment.body` through an environment variable and reference it safely within the script:\n\n```yaml\n- name: Extract identifiers\n  id: extract-identifiers\n  env:\n    COMMENT_BODY: ${{ github.event.comment.body }}\n  run: |\n    identifiers=$(echo \"$COMMENT_BODY\" | grep -oE '@njzjz-bot .*' | head -n1 | cut -c12- | xargs)\n    echo \"identifiers=$identifiers\" >> $GITHUB_OUTPUT",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "GitHub Actions",
      "name" : "njzjz/wenxian"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "last_affected" : "0.3.1"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/njzjz/wenxian/security/advisories/GHSA-r4fj-r33x-8v88"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-34243"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/njzjz/wenxian"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-20", "CWE-77", "CWE-78" ],
    "severity" : "CRITICAL",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-03-29T15:39:56Z",
    "nvd_published_at" : "2026-03-31T16:16:33Z"
  }
}