https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 16 Oct 2026 10:50:07 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-214990 EUVD-2026-214990 https://cve.radiocsirt.org/vuln/euvd-2026-214990 https://cve.radiocsirt.org/vuln/fkie_cve-2023-30623 <p>`embano1/wip` is a GitHub Action written in Bash. Prior to version 2, the `embano1/wip` action uses the `github.event.pull_request.title` parameter in an insecure way. The title parameter is used in a run statement - resulting in a command injection vulnerability due to string interpolation. This vulnerability can be triggered by any user on GitHub. They just need to create a pull request with a commit message containing an exploit. (Note that first-time PR requests will not be run - but the attacker can submit a valid PR before submitting an invalid PR). The commit can be genuine, but the commit message can be malicious. This can be used to execute code on the GitHub runners and can be used to exfiltrate any secrets used in the CI pipeline, including repository tokens. Version 2 has a fix for this issue.</p> <p>`embano1/wip` is a GitHub Action written in Bash. Prior to version 2, the `embano1/wip` action uses the `github.event.pull_request.title` parameter in an insecure way. The title parameter is used in a run statement - resulting in a command injection vulnerability due to string interpolation. This vulnerability can be triggered by any user on GitHub. They just need to create a pull request with a commit message containing an exploit. (Note that first-time PR requests will not be run - but the attacker can submit a valid PR before submitting an invalid PR). The commit can be genuine, but the commit message can be malicious. This can be used to execute code on the GitHub runners and can be used to exfiltrate any secrets used in the CI pipeline, including repository tokens. Version 2 has a fix for this issue.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2023-30623 https://cve.radiocsirt.org/vuln/ghsa-rg3q-prf8-qxmp <p><strong>Affected:</strong> GitHub Actions: embano1/wip</p> <p>## Summary The `embano1/wip` action uses the `github.event.pull_request.title` parameter in an insecure way. The title parameter is used in a run statement - resulting in a command injection vulnerability due to string interpolation.</p> <p>## Details and Impact This vulnerability can be triggered by any user on GitHub. They just need to create a pull request with a commit message containing an exploit. (Note that first-time PR requests will not be run - but the attacker can submit a valid PR before submitting an invalid PR). The commit can be genuine, but the commit message can be malicious.</p> <p>This can be used to execute code on the GitHub runners (potentially use it for crypto-mining, and waste your resources) and can be used to exfiltrate any secrets that you use in the CI pipeline (including repository tokens). [Here](https://securitylab.github.com/research/github-actions-untrusted-input/) is a set of blog posts by Github&#39;s security team explaining this issue.</p> <p>## How to update existing workflows</p> <p>Replace the following line in your workflow using this action with the `v2` branch name or commit pointing to this branch:</p> <p>```yaml uses: embano1/wip@v2 ```</p> <p>Or using the exact commit:</p> <p>```yaml uses: embano1/wip@c25450f77ed02c20d00b76ee3b33ff43838739a2 # v2 ```</p> <p><strong>Affected:</strong> GitHub Actions: embano1/wip</p> <p>## Summary The `embano1/wip` action uses the `github.event.pull_request.title` parameter in an insecure way. The title parameter is used in a run statement - resulting in a command injection vulnerability due to string interpolation.</p> <p>## Details and Impact This vulnerability can be triggered by any user on GitHub. They just need to create a pull request with a commit message containing an exploit. (Note that first-time PR requests will not be run - but the attacker can submit a valid PR before submitting an invalid PR). The commit can be genuine, but the commit message can be malicious.</p> <p>This can be used to execute code on the GitHub runners (potentially use it for crypto-mining, and waste your resources) and can be used to exfiltrate any secrets that you use in the CI pipeline (including repository tokens). [Here](https://securitylab.github.com/research/github-actions-untrusted-input/) is a set of blog posts by Github&#39;s security team explaining this issue.</p> <p>## How to update existing workflows</p> <p>Replace the following line in your workflow using this action with the `v2` branch name or commit pointing to this branch:</p> <p>```yaml uses: embano1/wip@v2 ```</p> <p>Or using the exact commit:</p> <p>```yaml uses: embano1/wip@c25450f77ed02c20d00b76ee3b33ff43838739a2 # v2 ```</p> https://cve.radiocsirt.org/vuln/ghsa-rg3q-prf8-qxmp https://cve.radiocsirt.org/vuln/gsd-2023-30623 gsd-2023-30623 https://cve.radiocsirt.org/vuln/gsd-2023-30623