Skip to main content
Mallory
MediumPublic exploitVulnerability

CVE-2026-35380: Incorrect delimiter interpretation in uutils coreutils cut

Published Apr 22, 2026 · Updated 23 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS5.5Medium · v3.1
EPSS0.16%5th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Uutils
IdentifiersCVE-2026-35380CWE-115

CVE-2026-35380 is an input-interpretation logic error in the cut utility of uutils coreutils. The utility incorrectly treats a literal two-byte string consisting of two single quotes as an empty delimiter and maps it to the NUL character when supplied to either -d or --output-delimiter. This can cause unintended field splitting or output joining, resulting in silent data corruption and incorrect behavior in automated scripts and data pipelines.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Incorrect delimiter handling can compromise the integrity of processed data. Input fields may be split on NUL bytes instead of the intended delimiter, or output fields may be joined using unintended NUL bytes. Downstream scripts and pipelines may consume incorrect results without detecting the error. No privilege escalation, code execution, or confidentiality impact is established.

Mitigation

If you can’t patch tonight, do this now.

Use GNU cut instead of the affected uutils implementation for affected workflows. Validate delimiter arguments and reject the literal two-single-quote string before passing it to either -d or --output-delimiter.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
UutilsCoreutilsapplication
FAQ

Frequently asked questions

Is CVE-2026-35380 exploited in the wild?
As of Oct 25, 2026, Mallory has no reports of CVE-2026-35380 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-35380?
Yes. As of Oct 25, 2026, Mallory has reports of a public exploit for CVE-2026-35380.
What products are affected by CVE-2026-35380?
Uutils Coreutils.
How severe is CVE-2026-35380?
CVE-2026-35380 has a CVSS v3.1 score of 5.5 (Medium) and an EPSS score of 0.16% (5th percentile) as of Oct 25, 2026.
Activity feed

Recent activity

1 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.

View more in app →

No news coverage yet. Advisories and community discussion only.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity1Community discussion across Reddit, Mastodon, and other social sources.