Loading vulnerability…
CVE-2026-35381 is a logic flaw in the Rust-based uutils coreutils implementation of the cut utility. The issue occurs when cut is invoked with zero-terminated input (-z or --zero-terminated), an empty delimiter specified with -d '', and the suppress-undelimited-records option (-s or --only-delimited). In affected versions, this option combination is routed through a specialized newline-delimiter handling path that fails to honor the only_delimited suppression state. As a result, records that should be suppressed under GNU/POSIX-compatible behavior are instead emitted in full, followed by a trailing NUL byte. The provided context identifies the vulnerable code path in the uu_cut implementation, specifically the cut_fields_newline_char_delim function in src/uu/cut/src/cut.rs, where mismatched parameter/configuration handling caused the utility to behave as though the -s flag were unset. Affected versions are described as uutils coreutils prior to 0.8.0.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.