CVE-2026-35369: uutils coreutils kill System-wide Process Termination and Denial of Service via Argument Misinterpretation

Published Apr 22, 2026
·
Updated

kill -1 is incorrectly parsed as a positional pid = -1; combined with the default SIGTERM this calls kill(-1, SIGTERM), signaling nearly every process the caller can see. GNU kill recognizes -1/-9 as signals and reports "not enough arguments".

$ kill -1 # uutils: kill(-1, SIGTERM) -> mass termination / crash $ kill -1 # GNU: kill: not enough arguments

Impact: a user running kill -1 mass-terminates processes, potentially crashing the system. Recommendation: parse -N as a signal number, and error with "not enough arguments" when no PID is given.

Remediation: Acknowledged by Canonical; fixed in commit cae94028.

--- Reported by Zellic in the uutils coreutils Program Security Assessment (prepared for Canonical, Jan 20 2026), audited commit 3a07ffc5a9bd4c283e75afa548ba1f1957bad242. Finding 3.70. Credit: Zellic.

Other sources

An argument parsing error in the kill utility of uutils coreutils incorrectly interprets kill -1 as a request to send the default signal (SIGTERM) to PID -1. Sending a signal to PID -1 causes the kernel to terminate all processes visible to the caller, potentially leading to a system crash or massive process termination. This differs from GNU coreutils, which correctly recognizes -1 as a signal number in this context and would instead report a missing PID argument.

MITRE

Affected Software

3 affected componentsFixes available
uutils uutils coreutils
uutils Coreutils Rust<0.6.0
rust/uu_kill<0.6.0
0.6.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade rust/uu_kill to a version that resolves this vulnerability.

    Fixed in 0.6.0
  2. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Patch cae94028
  3. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Patch 3a07ffc5a9bd4c283e75afa548ba1f1957bad242

Event History

Apr 22, 2026
CVE Published
via MITRE·04:08 PM
Data Sourced
via MITRE·04:08 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·05:16 PM
RemedyDescriptionSeverityWeaknessAffected Software
Jul 6, 2026
Advisory Published
via GitHub·07:55 PM
Data Sourced
via GitHub·07:55 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-35369?

CVE-2026-35369 has a high severity due to its potential to cause a system-wide denial of service.

2

How do I fix CVE-2026-35369?

To fix CVE-2026-35369, update to the latest version of uutils coreutils that addresses this vulnerability.

3

What kind of vulnerabilities does CVE-2026-35369 have?

CVE-2026-35369 has vulnerabilities related to argument misinterpretation in the kill utility leading to unintended process termination.

4

What impact does CVE-2026-35369 have on system security?

CVE-2026-35369 can impact system security by allowing unauthorized termination of critical processes, potentially leading to denial of service.

5

Is CVE-2026-35369 a local or remote vulnerability?

CVE-2026-35369 is a local vulnerability as it involves improper command usage that affects processes on the same system.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203