CVE-2025-5278: Coreutils: heap buffer under-read in gnu coreutils sort via key specification
A flaw was found in GNU Coreutils. The sort utility's begfield() function is vulnerable to a heap buffer under-read. The program may access memory outside the allocated buffer if a user runs a crafted command using the traditional key format. A malicious input could lead to a crash or leak sensitive data.
Security readout for executives and security teams
This is a flaw in GNU coreutils sort. If someone is tricked into running sort with a specially crafted traditional key format, the program may read memory outside its buffer. The likely business impact is localized crashes or limited information disclosure, not remote system takeover. Exposure is mainly Linux systems, containers, and platforms carrying affected coreutils packages, especially Red Hat-listed RHEL 8, 9, 10, OpenShift Container Platform 4, and named Red Hat containers. RHEL 6 and 7 status is listed as unknown in the provided data. Treat this as routine but timely patch work. It is not described as actively exploited, but coreutils is widely deployed and often present in base images, so unmanaged container and Linux fleet exposure can linger. Mitigation focus: Apply relevant Red Hat errata updates for affected RHEL, OpenShift, and container packages.; Review GNU coreutils vendor guidance and downstream distribution advisories before patching non-Red Hat systems.; Refresh affected container images that include vulnerable coreutils builds..
Prepared
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-121: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-121 · source CWE mapping
Stack-based Buffer Overflow
Stack-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.