Loading story…
An oss-sec disclosure reported that the Rust-based uutils coreutils project contains 113 audit findings, including 44 assigned CVEs (CVE-2026-35338 through CVE-2026-35381), after a Zellic review tied to Canonical's evaluation of the package for Ubuntu 26.04. Canonical said most issues had been resolved, but the report said multiple vulnerabilities were still reproducible on a fully updated Ubuntu 26.04 system running uutils coreutils 0.8.0. Because of TOCTOU race conditions, Canonical kept the GNU implementations of cp, mv, and rm rather than replacing them with uutils versions.
The published issues span mkfifo, nohup, tail, and other utilities, and include symlink attacks, unsafe file creation, permission and ownership handling flaws, incorrect exit codes, UTF-8 parsing bugs, and logic errors that could enable privilege escalation, information disclosure, denial of service, data corruption, or destructive filesystem operations. A follow-up oss-sec reply focused on the mkfifo case, agreeing that the race condition remained valid while clarifying that the example's initial FIFO permissions would be shaped by umask(002), producing mode 664 rather than 666 before a later chmod(2) call.
Mallory correlates global threat intelligence with your attack surface — know if you’re exposed before adversaries strike.
5 events from the most recent confirmed update back to the earliest known activity.
Ubuntu switched the cp command back to GNU coreutils after a compatibility bug in Rust coreutils cp broke Ubuntu image builds and live media ISO construction. The failure was tied to different handling of the "-L" argument, and an upstream fix had been proposed but not yet merged.
In a follow-up oss-sec discussion, Jan Schaumann said the reported mkfifo race condition was not in dispute but clarified that the initial FIFO permissions in the example would be affected by umask(002). He noted the FIFO would initially be mode 664 rather than 666, making it group-writable rather than world-writable before a later chmod(2) call.
Collin Funk reported that multiple vulnerabilities remained reproducible on a fully updated Ubuntu 26.04 system running uutils coreutils 0.8.0, including examples involving mkfifo, nohup, and a symlink-following issue in tail. The same disclosure enumerated CVE-2026-35338 through CVE-2026-35381 across affected uutils utilities.
Canonical said it would retain the GNU implementations of cp, mv, and rm in Ubuntu 26.04 rather than replace them with uutils versions because of TOCTOU race-condition concerns. Canonical also stated that most audit issues had been resolved, though it did not clearly specify which remained open.
A Zellic security audit of the Rust-based uutils coreutils project identified 113 issues, 44 of which were assigned CVEs. The findings covered race conditions, symlink attacks, permission and ownership flaws, unsafe file creation, logic errors, and other bugs affecting multiple utilities.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
5 references tracked. Mallory keeps watching after this page renders.
phoronix.com
Open sourceseclists.org
Open sourceseclists.org
Open sourceseclists.org
Open sourceseclists.org
Open sourceMap 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.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
CERT Polska disclosed two vulnerabilities in **GNU coreutils**, tracked as `CVE-2026-56391` and `CVE-2026-56392`. The notice identifies the flaws as affecting the widely used GNU core utilities package, a foundational component on many Linux and Unix-like systems, and indicates the issues were reported to CERT Polska for publication. Public reporting on the vulnerabilities remains limited, with the available references providing only the identifiers and confirming that two separate flaws were documented. No technical root cause, affected version range, exploitation details, or mitigation guidance were included in the cited notices, leaving organizations that rely on GNU coreutils to monitor vendor and CERT updates for patch and exposure information.
Jul 24, 2026
Multiple newly disclosed vulnerabilities exposed **arbitrary file write** paths through symlink handling and path validation failures in developer and server-side software. In **Crawl4AI** before `0.8.8`, `CVE-2026-56258` affects screenshot and PDF endpoints by combining weak `output_path` validation, symlink following, and a **TOCTOU** race, allowing unauthenticated remote attackers to write files outside the intended directory and potentially reach code execution. In **Cursor Desktop** before `3.0`, `CVE-2026-50549` lets a malicious agent escape the workspace sandbox by forcing path canonicalization to fail and then abusing an in-workspace symlink to write arbitrary files under the user’s privileges, including paths that could enable later unsandboxed execution. A related pattern also appeared in archive extraction and privileged upload handling. The **extract-zip** package is affected by `CVE-2026-56876`, which fails to validate symlink targets inside ZIP archives, enabling path traversal outside the extraction directory and possible arbitrary file read or write when processing untrusted archives. Separately, **pwnlift** disclosed `CVE-2026-56815` in a privileged upload handler that could be abused for arbitrary file write **as root** through direct symlink following and a TOCTOU race; an initial fix was bypassable before a follow-up patch was merged, while one downstream deployment mitigated exposure by removing the privileged `sudo` entry. Together, the disclosures highlight recurring risk from incomplete path canonicalization, unsafe symlink handling, and containment checks in file-write workflows.
Jul 2, 2026
CERT Polska disclosed three vulnerabilities in **GNU cpio** affecting versions through **2.15**, tracked as `CVE-2026-66484`, `CVE-2026-66485`, and `CVE-2026-66486`. The issues were reported by researchers from the **AFINE Team** and fixed in upstream commits. The most serious flaw allows **path traversal** during archive extraction, a weakness aligned with `CWE-22`, in which crafted file paths can escape the intended extraction directory and potentially overwrite or access files outside the restricted path. The additional bugs include an **uncontrolled memory allocation** issue mapped to `CWE-789` that can trigger a **stack overflow** and denial of service, and an **improper output escaping** flaw that can produce forged archive listings or inject terminal escape sequences. Together, the vulnerabilities expose users handling untrusted archives to file-system compromise, service disruption, and deceptive terminal output, underscoring the risk of insufficient pathname validation, unsafe memory handling, and unescaped archive metadata in command-line archive tools.
Aug 10, 2026