# CVE-2026-35381: uutils coreutils cut Local Logic Error and Data Integrity Issue in Output Filtering

> A logic error in uutils cut ignores the -s flag with specific options, causing data integrity issues in automated pipelines by emitting records that should be suppressed.

- **Severity:** Low 3.3 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Apr 2026
- **Updated:** 22 Apr 2026
- **Also known as:** DEBIAN-CVE-2026-35381, GHSA-pmfc-4wjj-gmhx, UBUNTU-CVE-2026-35381

## What is CVE-2026-35381?

CVE-2026-35381 is a low-severity vulnerability in Uutils coreutils, published on 22 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A logic error in the cut utility of uutils coreutils causes the utility to ignore the -s (only-delimited) flag when using the -z (null-terminated) and -d '' (empty delimiter) options together. The implementation incorrectly routes this specific combination through a specialized newline-delimiter code path that fails to check the record suppression status. Consequently, uutils cut emits the entire record plus a NUL byte instead of suppressing it. This divergence from GNU coreutils behavior creates a data integrity risk for automated pipelines that rely on cut -s to filter out undelimited data.

Weakness: CWE-684 (Incorrect Provision of Specified Functionality)

## Which versions are affected by CVE-2026-35381?

2 open source packages ship an affected version, including uu_cut. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `uu_cut` | crates.io | All versions | 0.8.0 |
| `uu_cut` | crates.io | All versions | 0.8.0 |

Products: Uutils Coreutils.

## How do I fix CVE-2026-35381?

Upgrade uu_cut to 0.8.0 or later.

## Is CVE-2026-35381 being exploited?

There is no known exploitation of CVE-2026-35381 in the wild and no public exploit code.

## Other vulnerabilities in Uutils coreutils

- [CVE-2026-35338](https://insights.sbomify.com/CVE-2026-35338/): uutils coreutils chmod Path Traversal Bypass of --preserve-root (high 7.3)
- [CVE-2026-35368](https://insights.sbomify.com/CVE-2026-35368/): uutils coreutils chroot Local Privilege Escalation and chroot Escape in via Name Service Switch (NSS) Injection (high 7.2)
- [CVE-2026-35341](https://insights.sbomify.com/CVE-2026-35341/): uutils coreutils mkfifo Unauthorized Permission Change on Existing Files (high 7.1)
- [CVE-2026-35352](https://insights.sbomify.com/CVE-2026-35352/): uutils coreutils mkfifo Privilege Escalation via TOCTOU Race Condition (high 7.0)
- [CVE-2026-35349](https://insights.sbomify.com/CVE-2026-35349/): uutils coreutils Path-Based Safety Bypass with --preserve-root (medium 6.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-35381 and fix it if it is affected.

What it is: CVE-2026-35381 is a low-severity vulnerability in Uutils coreutils, published on 22 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-35381 in the wild and no public exploit code.

Affected packages and fixed versions:
- uu_cut (crates.io): affected all versions; fixed in 0.8.0
- uu_cut (crates.io): affected all versions; fixed in 0.8.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-35381/ (Markdown: https://insights.sbomify.com/CVE-2026-35381/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-35381
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-35381
- OSV: https://osv.dev/vulnerability/CVE-2026-35381

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-35381/
Summaries are generated and may contain mistakes; the official description above is the record.