Skip to main content
VulnerabilityPublished Updated

CVE-2026-35380: uutils coreutils has an Improper Input Validation Issue in its cut Utility

Affects coreutilsSource GCVE Database

0
Authoritative record:CVE-2026-35380· Medium 5.5

Not known to be exploited · CVSS 5.5 Medium : upgrade to 0.8.0 when convenient.

Data as of 27 Oct 2026, 00:27 UTC

CVSS 3.1 base score
5.5Medium
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 0.8.0
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 22 Apr 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade coreutils to 0.8.0.

Affected software

ProductAffectedFixed in
crates.iocoreutilsAffected
  • <0.8.0
Fixed in
  • 0.8.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade uutils coreutils to version 0.8.0 or later where this issue is fixed. Since a patch is available, applying the official fix eliminates the vulnerability. No other mitigation is indicated.

Description

CVE-2026-35380 is a logic error vulnerability in the cut utility of uutils coreutils prior to version 0.8.0. The utility incorrectly treats the two-byte string of two single quotes ('') as an empty delimiter, mapping it to the NUL character for both the -d and --output-delimiter options. This can cause silent data corruption or logic errors in automated scripts and data pipelines that rely on literal delimiters, as the utility may split or join data on NUL bytes instead of the intended characters. The issue is fixed in version 0.8.0.

References

Community reviews

Loading reviews…