Skip to main content
VulnerabilityPublished

CVE-2026-35380: Uutils coreutils · Improper Input Validation

Affects Uutils coreutilsSource CVE Database V5

0
Compare

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

Data as of 30 Oct 2026, 06:59 UTC

CVSS 3.1 base score
5.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 4% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
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. Weaponized: 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 29 Oct 2026.

What to do

Upgrade Uutils coreutils to 0.8.0.

Affected software

ProductAffectedFixed in
UutilscoreutilsAffected
  • <0.8.0
Fixed in
  • 0.8.0
GitHubuutils/coreutilspkg:github/uutils/coreutilsOther threatsAffected
  • =0
Fixed in–
GitHubcoreutilspkg:github/coreutilsOther threatsAffected
  • <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

If you cannot patch yet, users should avoid using the two single quote string ('') as a delimiter with the cut utility in uutils coreutils or validate outputs carefully to detect potential data corruption.

Description

A logic error in the cut utility of uutils coreutils causes the program to incorrectly interpret the literal two-byte string '' (two single quotes) as an empty delimiter. The implementation mistakenly maps this string to the NUL character for both the -d (delimiter) and --output-delimiter options. This vulnerability can lead to silent data corruption or logic errors in automated scripts and data pipelines that process strings containing these characters, as the utility may unintentionally split or join data on NUL bytes rather than the intended literal characters.

References

Community reviews

Loading reviews…