GHSA-6p2j-742g-835f: actions-mkdocs Command Injection Vulnerability

MODERATE
CVSS 6.5
CWE-77
Published
Advisory Summary

GHSA-6p2j-742g-835f is a MODERATE (CVSS 6.5) command injection vulnerability (CWE-77: Improper Neutralization of Special Elements used in a Command ('Command Injection')) affecting actions-mkdocs libraries in the GitHub Actions ecosystem. The issue involves command injection via issue title in internal github actions workflow. Remediation is available by upgrading affected packages to version 0.25.0.

GHSA-6p2j-742g-835f at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-6p2j-742g-835f
Severity MODERATE
CVSS v3.1 Base Score 6.5
CWE Classification CWE-77: Improper Neutralization of Special Elements used in a Command ('Command Injection')
Affected Product actions-mkdocs
Package Ecosystem GitHub Actions
Published Date
Last Updated

Security Impact

CVSS: 6.5

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

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 Low (C:L)
Integrity Low (I:L)
Availability None (A:N)

How to Fix GHSA-6p2j-742g-835f

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

Tiryoh/actions-mkdocs fixed: 0.25.0
Upgrade Tiryoh/actions-mkdocs to 0.25.0
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 Tiryoh/actions-mkdocs

How to Check if You Are Affected

To determine whether your application is affected by GHSA-6p2j-742g-835f, inspect your project dependencies for actions-mkdocs:

inspect dependencies for Tiryoh/actions-mkdocs

Analyze the terminal output to locate any version of actions-mkdocs in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.25.0), 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-77: Improper Neutralization of Special Elements used in a Command ('Command Injection'), where 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. In actions-mkdocs, 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 External input from `github.event.issue.title` is used unsafely in a shell command in `.github/workflows/release-candidate.yaml`, allowing command injection during workflow execution. ### Details In `.github/workflows/release-candidate.yaml`, the issue title is interpolated directly into a shell command: ``` export VERSION=$(echo ${{ github.event.issue.title }} | sed -E 's/Release v?([0-9\.]*)/\1/g') ``` Because the issue title is attacker-controlled and is embedded directly into a shell command, shell metacharacters such as command substitution (`$()`) and command separators (`;`) can be interpreted by the shell. Although the workflow checks that the title starts with `Release `, this condition can still be satisfied by a maliciously crafted input. ### PoC 1. Create or edit an issue with the following title: ``` Release v1.2.3 $(whoami) ``` 2. Trigger the workflow that processes the issue. 3. Observe that the injected command is executed on the runner. The workflow logs show that `$(whoami)` is evaluated and its output (`runner`) appears in the command result, confirming that attacker-controlled input is executed within the shell. <img width="633" height="380" alt="스크린샷 2026-03-27 오후 8 33 43" src="https://github.com/user-attachments/assets/90b38dab-8c53-4a13-8302-158ac5acf051" /> ### Impact This vulnerability allows command injection in the GitHub Actions runner through attacker-controlled issue titles. An attacker may be able to execute arbitrary commands within the context of the affected workflow job. Depending on the workflow configuration (such as permissions and available secrets), successful exploitation could lead to: * Unauthorized command execution in the CI environment * Misuse of the `GITHUB_TOKEN` * Modification of repository state, release artifacts, or other workflow outputs If the repository is public and allows untrusted users to create or reopen issues that trigger the workflow, this may be exploitable by external users. This issue is limited to the repository's internal workflow configuration and does not directly affect downstream users of the published `actions-mkdocs` GitHub Action.

GHSA-6p2j-742g-835f Affected actions-mkdocs Versions

1 component(s)
Fixed Versions:
0.25.0
Product / Package Ecosystem Affected Versions Fixed Version
Tiryoh/actions-mkdocs
GitHub Actions
< 0.25.0
0.25.0

References

Frequently Asked Questions

What is GHSA-6p2j-742g-835f?
GHSA-6p2j-742g-835f is a security vulnerability in actions-mkdocs involving Command Injection via issue title in internal GitHub Actions workflow under CWE-77: Improper Neutralization of Special Elements used in a Command ('Command Injection').
Which actions-mkdocs versions are affected?
Affected versions include releases prior to 0.25.0 across affected packages: Tiryoh/actions-mkdocs.
What version fixes GHSA-6p2j-742g-835f?
Upgrading to 0.25.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is Tiryoh/actions-mkdocs affected?
Yes, Tiryoh/actions-mkdocs is affected in releases prior to 0.25.0. Upgrade your dependency to 0.25.0 or later.
What is the CVSS score of GHSA-6p2j-742g-835f?
GHSA-6p2j-742g-835f has a CVSS v3.1 base score of 6.5 (MODERATE) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N.
What CWE is associated with GHSA-6p2j-742g-835f?
GHSA-6p2j-742g-835f is classified under CWE-77: Improper Neutralization of Special Elements used in a Command ('Command Injection') (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.).
How can I check GitHub Actions dependencies for GHSA-6p2j-742g-835f?
Run the dependency tree command: 'inspect dependencies for Tiryoh/actions-mkdocs'. 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-6p2j-742g-835f",
  "modified" : "2026-04-04T06:03:06Z",
  "published" : "2026-04-04T06:03:06Z",
  "aliases" : [ ],
  "summary" : "actions-mkdocs: Command Injection via issue title in internal GitHub Actions workflow",
  "details" : "### Summary\n\nExternal input from `github.event.issue.title` is used unsafely in a shell command in `.github/workflows/release-candidate.yaml`, allowing command injection during workflow execution.\n\n### Details\n\nIn `.github/workflows/release-candidate.yaml`, the issue title is interpolated directly into a shell command:\n\n```\nexport VERSION=$(echo ${{ github.event.issue.title }} | sed -E 's/Release v?([0-9\\.]*)/\\1/g')\n```\n\nBecause the issue title is attacker-controlled and is embedded directly into a shell command, shell metacharacters such as command substitution (`$()`) and command separators (`;`) can be interpreted by the shell.\n\nAlthough the workflow checks that the title starts with `Release `, this condition can still be satisfied by a maliciously crafted input.\n\n### PoC\n\n1. Create or edit an issue with the following title:\n\n   ```\n   Release v1.2.3 $(whoami)\n   ```\n\n2. Trigger the workflow that processes the issue.\n\n3. Observe that the injected command is executed on the runner.\n\nThe workflow logs show that `$(whoami)` is evaluated and its output (`runner`) appears in the command result, confirming that attacker-controlled input is executed within the shell.\n\n<img width=\"633\" height=\"380\" alt=\"스크린샷 2026-03-27 오후 8 33 43\" src=\"https://github.com/user-attachments/assets/90b38dab-8c53-4a13-8302-158ac5acf051\" />\n\n\n### Impact\n\nThis vulnerability allows command injection in the GitHub Actions runner through attacker-controlled issue titles. An attacker may be able to execute arbitrary commands within the context of the affected workflow job.\n\nDepending on the workflow configuration (such as permissions and available secrets), successful exploitation could lead to:\n\n* Unauthorized command execution in the CI environment\n* Misuse of the `GITHUB_TOKEN`\n* Modification of repository state, release artifacts, or other workflow outputs\n\nIf the repository is public and allows untrusted users to create or reopen issues that trigger the workflow, this may be exploitable by external users.\n\nThis issue is limited to the repository's internal workflow configuration and does not directly affect downstream users of the published `actions-mkdocs` GitHub Action.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "GitHub Actions",
      "name" : "Tiryoh/actions-mkdocs"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.25.0"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 0.24.0"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/Tiryoh/actions-mkdocs/security/advisories/GHSA-6p2j-742g-835f"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/Tiryoh/actions-mkdocs"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-77" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-04-04T06:03:06Z",
    "nvd_published_at" : null
  }
}