https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 12:13:22 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-158393 EUVD-2026-158393 https://cve.radiocsirt.org/vuln/euvd-2026-158393 https://cve.radiocsirt.org/vuln/fkie_cve-2024-42482 <p>fish-shop/syntax-check is a GitHub action for syntax checking fish shell files. Improper neutralization of delimiters in the `pattern` input (specifically the command separator `;` and command substitution characters `(` and `)`) mean that arbitrary command injection is possible by modification of the input value used in a workflow. This has the potential for exposure or exfiltration of sensitive information from the workflow runner, such as might be achieved by sending environment variables to an external entity. It is recommended that users update to the patched version `v1.6.12` or the latest release version `v2.0.0`, however remediation may be possible through careful control of workflows and the `pattern` input value used by this action.</p> <p>fish-shop/syntax-check is a GitHub action for syntax checking fish shell files. Improper neutralization of delimiters in the `pattern` input (specifically the command separator `;` and command substitution characters `(` and `)`) mean that arbitrary command injection is possible by modification of the input value used in a workflow. This has the potential for exposure or exfiltration of sensitive information from the workflow runner, such as might be achieved by sending environment variables to an external entity. It is recommended that users update to the patched version `v1.6.12` or the latest release version `v2.0.0`, however remediation may be possible through careful control of workflows and the `pattern` input value used by this action.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2024-42482 https://cve.radiocsirt.org/vuln/ghsa-xj87-mqvh-88w2 <p><strong>Affected:</strong> GitHub Actions: fish-shop/syntax-check</p> <p>### Impact</p> <p>Improper neutralisation of delimiters in the `pattern` input (specifically the command separator `;` and command substitution characters `(` and `)`) mean that arbitrary command injection is possible by modification of the input value used in a workflow. This has the potential for exposure or exfiltration of sensitive information from the workflow runner, such as might be achieved by sending environment variables to an external entity.</p> <p>### Patches</p> <p>As of this writing, the issue has been patched for versions in the `v1.x.x` release series in release `v1.6.12` (also tagged as `v1.6` and `v1`). The latest available release `v2.0.0` also includes a corresponding patch (also tagged as `v2.0` and `v2`).</p> <p>Users should upgrade to at least the patched version `v1.6.12` or preferably the latest available version `v2.0.0`. Workflows that use the action ref `v1` will automatically receive the patched version `v1.6.12` in future workflow runs.</p> <p>Patch summary:</p> <p>| Release series | Patched tags | Patched commit hashes | |----------------|-------------------------|-------------| | `1.x.x` | `v1.6.12`, `v1.6`, `v1` | `91e6817c48ad475542fe4e78139029b036a53b03` | | `2.x.x` | `v2.0.0`, `v2.0`, `v2` | `c2cb11395e21119ff8d6e7ea050430ee7d6f49ca` |</p> <p>### Workarounds</p> <p>Is it recommended that users update to the patched version `v1.6.12` or the latest release version `v2.0.0`, however remediation may be possible through careful control of workflows and the `pattern`…</p> <p><strong>Affected:</strong> GitHub Actions: fish-shop/syntax-check</p> <p>### Impact</p> <p>Improper neutralisation of delimiters in the `pattern` input (specifically the command separator `;` and command substitution characters `(` and `)`) mean that arbitrary command injection is possible by modification of the input value used in a workflow. This has the potential for exposure or exfiltration of sensitive information from the workflow runner, such as might be achieved by sending environment variables to an external entity.</p> <p>### Patches</p> <p>As of this writing, the issue has been patched for versions in the `v1.x.x` release series in release `v1.6.12` (also tagged as `v1.6` and `v1`). The latest available release `v2.0.0` also includes a corresponding patch (also tagged as `v2.0` and `v2`).</p> <p>Users should upgrade to at least the patched version `v1.6.12` or preferably the latest available version `v2.0.0`. Workflows that use the action ref `v1` will automatically receive the patched version `v1.6.12` in future workflow runs.</p> <p>Patch summary:</p> <p>| Release series | Patched tags | Patched commit hashes | |----------------|-------------------------|-------------| | `1.x.x` | `v1.6.12`, `v1.6`, `v1` | `91e6817c48ad475542fe4e78139029b036a53b03` | | `2.x.x` | `v2.0.0`, `v2.0`, `v2` | `c2cb11395e21119ff8d6e7ea050430ee7d6f49ca` |</p> <p>### Workarounds</p> <p>Is it recommended that users update to the patched version `v1.6.12` or the latest release version `v2.0.0`, however remediation may be possible through careful control of workflows and the `pattern`…</p> https://cve.radiocsirt.org/vuln/ghsa-xj87-mqvh-88w2