VulnerabilityPublished 22 Apr 2026

CVE-2026-35343: Uutils coreutils · Always-Incorrect Control Flow Implementation

Affects Uutils coreutilsSource CVE Database V5

Compare

Not known to be exploited · CVSS 3.3 Low : upgrade to 0.8.0 when convenient.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 3.1 base score

3.3Low

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 2% 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:L/A:N

Attack Vector: Local
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 22 Apr 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Uutils coreutils to 0.8.0.

Affected software

Product	Affected	Fixed in
Uutilscoreutils	Affected <0.8.0	Fixed in 0.8.0
GitHubuutils/coreutils`pkg:github/uutils/coreutils`Other threats	Affected =0	Fixed in–
GitHubcoreutils`pkg:github/coreutils`Other threats	Affected <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 be cautious when using the -s option with newline delimiters in the cut utility of uutils coreutils. Consider alternative tools or manual verification of output to ensure data integrity.

Description

A vulnerability in the cut utility of uutils coreutils causes incorrect handling of the -s (only-delimited) option when a newline character is used as the delimiter. This flaw results in non-delimited lines being printed when they should be suppressed, potentially passing unexpected data to downstream scripts relying on strict output filtering. The issue is identified as CWE-670 (Always-Incorrect Control Flow Implementation). The vulnerability has a low severity score and no known exploits or patches are currently available.

Impact

The vulnerability can cause the cut utility to output lines that should have been suppressed, potentially leading to unexpected or unintended data being passed to downstream scripts or processes. This may affect the integrity of data processing pipelines relying on strict delimiter-based filtering. There is no impact on confidentiality or availability, and no known exploits in the wild have been reported.

Summary

CVE-2026-35343 describes a control flow implementation flaw in the cut utility of uutils coreutils. Specifically, when the -s option is used with a newline delimiter, the function cut_fields_newline_char_delim fails to verify the only_delimited flag properly. This causes the utility to output lines that do not contain the delimiter, contrary to expected behavior. The incorrect control flow leads to unexpected data leakage to downstream processes that depend on filtered output. The vulnerability is rated low severity with a CVSS score of 3.3 and currently has no official remediation or patch available.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 7 Jul 2026, 12:35 UTC

WeaknessesCWE-670

Technical details

References

Community reviews

Related threats