https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 09 Oct 2026 22:34:26 +0000 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0967 certfr-2025-avi-0967 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0967 https://cve.radiocsirt.org/vuln/euvd-2026-248537 EUVD-2026-248537 https://cve.radiocsirt.org/vuln/euvd-2026-248537 https://cve.radiocsirt.org/vuln/fkie_cve-2024-58266 <p>The shlex crate before 1.2.1 for Rust allows unquoted and unescaped instances of the { and \xa0 characters, which may facilitate command injection.</p> <p>The shlex crate before 1.2.1 for Rust allows unquoted and unescaped instances of the { and \xa0 characters, which may facilitate command injection.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2024-58266 https://cve.radiocsirt.org/vuln/ghsa-r7qv-8r2h-pg27 <p><strong>Affected:</strong> crates.io: shlex</p> <p>## Issue 1: Failure to quote characters</p> <p>Affected versions of this crate allowed the bytes `{` and `\xa0` to appear unquoted and unescaped in command arguments.</p> <p>If the output of `quote` or `join` is passed to a shell, then what should be a single command argument could be interpreted as multiple arguments.</p> <p>This does not *directly* allow arbitrary command execution (you can&#39;t inject a command substitution or similar). But depending on the command you&#39;re running, being able to inject multiple arguments where only one is expected could lead to undesired consequences, potentially including arbitrary command execution.</p> <p>The flaw was corrected in version 1.2.1 by escaping additional characters. Updating to 1.3.0 is recommended, but 1.2.1 offers a more minimal fix if desired.</p> <p>Workaround: Check for the bytes `{` and `\xa0` in `quote`/`join` input or output.</p> <p>(Note: `{` is problematic because it is used for glob expansion. `\xa0` is problematic because it&#39;s treated as a word separator in [specific environments][solved-xa0].)</p> <p>## Issue 2: Dangerous API w.r.t. nul bytes</p> <p>Version 1.3.0 deprecates the `quote` and `join` APIs in favor of `try_quote` and `try_join`, which behave the same except that they have `Result` return type, returning `Err` if the input contains nul bytes.</p> <p>Strings containing nul bytes generally cannot be used in Unix command arguments or environment variables, and most shells cannot handle nul bytes even internally. If you try to pass one anyway, then the resu…</p> <p><strong>Affected:</strong> crates.io: shlex</p> <p>## Issue 1: Failure to quote characters</p> <p>Affected versions of this crate allowed the bytes `{` and `\xa0` to appear unquoted and unescaped in command arguments.</p> <p>If the output of `quote` or `join` is passed to a shell, then what should be a single command argument could be interpreted as multiple arguments.</p> <p>This does not *directly* allow arbitrary command execution (you can&#39;t inject a command substitution or similar). But depending on the command you&#39;re running, being able to inject multiple arguments where only one is expected could lead to undesired consequences, potentially including arbitrary command execution.</p> <p>The flaw was corrected in version 1.2.1 by escaping additional characters. Updating to 1.3.0 is recommended, but 1.2.1 offers a more minimal fix if desired.</p> <p>Workaround: Check for the bytes `{` and `\xa0` in `quote`/`join` input or output.</p> <p>(Note: `{` is problematic because it is used for glob expansion. `\xa0` is problematic because it&#39;s treated as a word separator in [specific environments][solved-xa0].)</p> <p>## Issue 2: Dangerous API w.r.t. nul bytes</p> <p>Version 1.3.0 deprecates the `quote` and `join` APIs in favor of `try_quote` and `try_join`, which behave the same except that they have `Result` return type, returning `Err` if the input contains nul bytes.</p> <p>Strings containing nul bytes generally cannot be used in Unix command arguments or environment variables, and most shells cannot handle nul bytes even internally. If you try to pass one anyway, then the resu…</p> https://cve.radiocsirt.org/vuln/ghsa-r7qv-8r2h-pg27 https://cve.radiocsirt.org/vuln/msrc_cve-2024-58266 msrc_CVE-2024-58266 https://cve.radiocsirt.org/vuln/msrc_cve-2024-58266 https://cve.radiocsirt.org/vuln/opensuse-su-2025:15433-1 <p>framework-inputmodule-control-0.2.0-3.1 on GA media</p> <p>framework-inputmodule-control-0.2.0-3.1 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2025:15433-1 https://cve.radiocsirt.org/vuln/rustsec-2024-0006 <p><strong>Affected:</strong> crates.io: shlex</p> <p>## Issue 1: Failure to quote characters</p> <p>Affected versions of this crate allowed the bytes `{` and `\xa0` to appear unquoted and unescaped in command arguments.</p> <p>If the output of `quote` or `join` is passed to a shell, then what should be a single command argument could be interpreted as multiple arguments.</p> <p>This does not *directly* allow arbitrary command execution (you can&#39;t inject a command substitution or similar). But depending on the command you&#39;re running, being able to inject multiple arguments where only one is expected could lead to undesired consequences, potentially including arbitrary command execution.</p> <p>The flaw was corrected in version 1.2.1 by escaping additional characters. Updating to 1.3.0 is recommended, but 1.2.1 offers a more minimal fix if desired.</p> <p>Workaround: Check for the bytes `{` and `\xa0` in `quote`/`join` input or output.</p> <p>(Note: `{` is problematic because it is used for glob expansion. `\xa0` is problematic because it&#39;s treated as a word separator in [specific environments][solved-xa0].)</p> <p>## Issue 2: Dangerous API w.r.t. nul bytes</p> <p>Version 1.3.0 deprecates the `quote` and `join` APIs in favor of `try_quote` and `try_join`, which behave the same except that they have `Result` return type, returning `Err` if the input contains nul bytes.</p> <p>Strings containing nul bytes generally cannot be used in Unix command arguments or environment variables, and most shells cannot handle nul bytes even internally. If you try to pass one anyway, then the resu…</p> <p><strong>Affected:</strong> crates.io: shlex</p> <p>## Issue 1: Failure to quote characters</p> <p>Affected versions of this crate allowed the bytes `{` and `\xa0` to appear unquoted and unescaped in command arguments.</p> <p>If the output of `quote` or `join` is passed to a shell, then what should be a single command argument could be interpreted as multiple arguments.</p> <p>This does not *directly* allow arbitrary command execution (you can&#39;t inject a command substitution or similar). But depending on the command you&#39;re running, being able to inject multiple arguments where only one is expected could lead to undesired consequences, potentially including arbitrary command execution.</p> <p>The flaw was corrected in version 1.2.1 by escaping additional characters. Updating to 1.3.0 is recommended, but 1.2.1 offers a more minimal fix if desired.</p> <p>Workaround: Check for the bytes `{` and `\xa0` in `quote`/`join` input or output.</p> <p>(Note: `{` is problematic because it is used for glob expansion. `\xa0` is problematic because it&#39;s treated as a word separator in [specific environments][solved-xa0].)</p> <p>## Issue 2: Dangerous API w.r.t. nul bytes</p> <p>Version 1.3.0 deprecates the `quote` and `join` APIs in favor of `try_quote` and `try_join`, which behave the same except that they have `Result` return type, returning `Err` if the input contains nul bytes.</p> <p>Strings containing nul bytes generally cannot be used in Unix command arguments or environment variables, and most shells cannot handle nul bytes even internally. If you try to pass one anyway, then the resu…</p> https://cve.radiocsirt.org/vuln/rustsec-2024-0006 https://cve.radiocsirt.org/vuln/suse-su-2025:20717-1 <p>Security update for rust-keylime</p> <p>Security update for rust-keylime</p> https://cve.radiocsirt.org/vuln/suse-su-2025:20717-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-58266 <p><strong>Affected:</strong> Ubuntu:20.04:LTS: rust-shlex, Ubuntu:22.04:LTS: rust-shlex, Ubuntu:24.04:LTS: rust-shlex, Ubuntu:25.10: rust-shlex, Ubuntu:26.04:LTS: rust-shlex</p> <p>The shlex crate before 1.2.1 for Rust allows unquoted and unescaped instances of the { and \xa0 characters, which may facilitate command injection.</p> <p><strong>Affected:</strong> Ubuntu:20.04:LTS: rust-shlex, Ubuntu:22.04:LTS: rust-shlex, Ubuntu:24.04:LTS: rust-shlex, Ubuntu:25.10: rust-shlex, Ubuntu:26.04:LTS: rust-shlex</p> <p>The shlex crate before 1.2.1 for Rust allows unquoted and unescaped instances of the { and \xa0 characters, which may facilitate command injection.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-58266