Findings

CVE-2026-58502

githubtoplanguages: Command Injection via Issue Title in Discord Notification Workflow

Published Jun 19, 2026 · updated Sep 17, 2026

### Summary A GitHub Actions workflow is vulnerable to command injection through the issue title. The workflow is triggered when an issue is opened or closed, and it directly inserts into a Bash variable assignment. If an issue title contains command substitution syntax, Bash evaluates it during the workflow run. ### Details The vulnerable workflow is: The issue title is directly interpolated into a Bash script: Because GitHub Actions expressions are expanded before Bash executes the script, an attacker-controlled issue title containing command substitution syntax can be evaluated by the shell. In the original workflow, the resulting value is then included in a Discord notification payload: ### PoC For safety, I reproduced this only in my fork. I did not trigger the original repository’s Discord webhook. I kept the vulnerable Bash assignment unchanged and replaced the Discord webhook request with statements to observe the result safely. Test issue title: Observed workflow log: This confirms that was executed on the GitHub Actions runner before the value would be sent to Discord. ### Impact Any user who can open an issue may be able to execute shell commands on the GitHub Actions runner. In practice, this means an attacker could create an issue with a crafted title, cause the workflow to execute a shell command, and have the command output included in the Discord notification content. This can be used to manipulate Discord notifications, spoof trusted GitHub bot messages, or repeatedly trigger unwanted notifications. More importantly, the command runs in a workflow environment where a Discord webhook secret is configured. Depending on repository settings and workflow permissions, this may put workflow secrets or other environment data at risk. ### Suggested Fix Do not insert issue titles directly into Bash scripts. Pass the title through an environment variable instead: Also avoid , unquoted variable expansion, or shell execution patterns involving user-controlled is