Skip to content

Duplicate Advisory: uutils coreutils has an Issue With its Always-Incorrect Control Flow Implementation

Low severity GitHub Reviewed Published Apr 22, 2026 to the GitHub Advisory Database • Updated Jul 6, 2026
Withdrawn This advisory was withdrawn on Jul 6, 2026

Package

cargo coreutils (Rust)

Affected versions

< 0.7.0

Patched versions

0.7.0

Description

Duplicate Advisory

This advisory has been withdrawn because it is a duplicate of GHSA-wv33-5pxh-r7j7. This link is maintained to preserve external references.

Original Description

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.

References

Published by the National Vulnerability Database Apr 22, 2026
Published to the GitHub Advisory Database Apr 22, 2026
Reviewed Apr 29, 2026
Last updated Jul 6, 2026
Withdrawn Jul 6, 2026

Severity

Low

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

EPSS score

Weaknesses

Always-Incorrect Control Flow Implementation

The code contains a control flow path that does not reflect the algorithm that the path is intended to implement, leading to incorrect behavior any time this path is navigated. Learn more on MITRE.

CVE ID

No known CVE

GHSA ID

GHSA-hj9r-8pfm-rmjj

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.