Cyber Resilience

CVE-2026-35343

Uutils Coreutils ≤ 0.7.0

Published
22 April 2026
Modified
04 May 2026
Patch / advisory
View advisory
CVSS Score v3.1 3.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
EPSS Score 0.0014 3th percentile
Risk Priority 15 floored blend · peak EPSS

Summary

CVE-2026-35343 is a low-severity Always-Incorrect Control Flow Implementation (CWE-670) vulnerability in Uutils Coreutils. Its CVSS base score is 3.3 (Low).

Operationally, ranked at the 3th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

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…

more

that should have been suppressed. This can lead to unexpected data being passed to downstream scripts that rely on strict output filtering.

CWE(s)
CWE-670

Related Threats

MITRE ATT&CK Enterprise TechniquesAI

Insufficient information to map techniques.
Confidence: LOW · MITRE ATT&CK Enterprise v19.0

CVEs Like This One

CVE-2026-35352Same product: Uutils Coreutils
CVE-2026-35347Same product: Uutils Coreutils
CVE-2026-35377Same product: Uutils Coreutils
CVE-2026-35356Same product: Uutils Coreutils
CVE-2026-35338Same product: Uutils Coreutils
CVE-2026-35365Same product: Uutils Coreutils
CVE-2026-35359Same product: Uutils Coreutils
CVE-2026-35340Same product: Uutils Coreutils
CVE-2026-35353Same product: Uutils Coreutils
CVE-2026-35362Same product: Uutils Coreutils

Affected Assets

uutils
coreutils
≤ 0.7.0

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
  • SI-10 Information Input Validation
  • SA-11 Developer Testing and Evaluation
Detect
Catch it (NIST detect / respond)
  • SI-2 Flaw Remediation
Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V9.2.1

Mitigating Controls (NIST 800-53 r5) AI

SI-10 Information Input Validation good match
prevent

Directly enforces correct validation/filtering logic so that the only_delimited flag suppresses non-matching lines for every delimiter including newline.

SA-11 Developer Testing and Evaluation good match
prevent

Requires systematic developer testing of security-critical paths such as flag handling in cut_fields_newline_char_delim, exposing the missing check before release.

SI-2 Flaw Remediation partial match
respond

Mandates prompt patching of the identified logic flaw in uutils coreutils once the CVE is published.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly prevent incorrect control-flow implementations via reviews, testing, and static analysis.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
detects

Security testing in development and acceptance can detect paths that deviate from intended logic.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle processes can catch incorrect control-flow logic during design and code review.

A.8.28 Secure coding partial match
prevents

Secure coding standards and reviews directly target flawed control-flow implementations.

A.8.32 Change management partial match
prevents

Change-management gates may prevent deployment of flawed logic but do not address the coding defect itself.

References