GNU released Coreutils 9.12, delivering 288 commits from 16 contributors and fixes for multiple memory-safety and reliability defects in foundational GNU command-line utilities. The release addresses a CWE-126 possible buffer over-read in factor; freed-memory reads in ls --color; heap-buffer overflows in unexpand; and read-buffer or lookup-table over-reads affecting uniq and wc. It also resolves long-standing recursive traversal failures in chcon, chgrp, chmod, chown, du, and ls when files are removed concurrently.
The update fixes infinite-loop and hang conditions in ptx, tee, shred, and truncate, while improving filesystem handling and performance in cut, uniq, and sort, including better handling of piped input. New features include env --env0-from=FILE for environment persistence, safer quoting and terminal-output behavior, and labeled uname output. Organizations packaging or operating GNU/Linux systems should prioritize testing and deploying Coreutils 9.12 where affected utilities process untrusted, malformed, or concurrently changing files and input.

See affected versions and whether adversaries are exploiting it.
1 event from the most recent confirmed update back to the earliest known activity.
GNU released stable GNU Coreutils 9.12, incorporating 288 commits from 16 contributors since version 9.11. The release adds new functionality and fixes robustness and security-relevant defects, including buffer over-read, freed-memory-read, overflow, hang, and recursive traversal issues.
See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
2 references tracked. Mallory keeps watching after this page renders.
Map indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.