cut: -s (only-delimited) ignored when delimiter is a newline
The cut utility in uutils coreutils incorrectly handles the -s (only-delimited) option when a newline character is specified as the delimiter. The implementation fails to verify the only_delimited flag in the cut_fields_newline_char_delim function, causing the utility to print non-delimited lines that should have been suppressed. This can lead to unexpected data being passed to downstream scripts that rely on strict output filtering. --- _Zellic finding 3.22. Reported in the Zellic *uutils coreutils Program Security Assessment* (for Canonical, Jan 2026), audited commit `3a07ffc5a9bd4c283e75afa548ba1f1957bad242`._
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2026-35343US | — | — | ||
The cut utility in uutils coreutils incorrectly handles the -s (only-delimited) option when a newline character is specified as the delimiter. The implementation fails to verify th… | ||||
references
External citations — patches, advisories, analysis.
- https://github.com/uutils/coreutilsPACKAGE
- https://github.com/uutils/coreutils/commit/9bbb58b746c41802278b0cba738eebbf21517cf7WEB
- https://github.com/uutils/coreutils/pull/11143WEB
- https://github.com/uutils/coreutils/releases/tag/0.7.0WEB
- https://github.com/uutils/coreutils/security/advisories/GHSA-wv33-5pxh-r7j7WEB
- https://nvd.nist.gov/vuln/detail/CVE-2026-35343ADVISORY
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan