Loading story…
The Rust Security Response Team disclosed Cargo vulnerabilities tracked as CVE-2026-5222 and CVE-2026-5223, highlighting risks in how Rust tooling processes package archives from third-party registries. In the published details for CVE-2026-5223, Cargo was found to mishandle symlinks inside crate tarballs, allowing a malicious crate to overwrite the cached source of another crate from the same registry by extracting files outside its intended cache path. The issue does not affect crates.io, which already blocks crates containing symlinks, but it affects Cargo versions shipped before Rust 1.96.0; the fix rejects extraction of any symlink found in crate tarballs.
The disclosures align with a separate advisory affecting the Rust package astral-tokio-tar, where a PAX header desynchronization bug in versions before 0.6.2 can cause tar archives to be interpreted differently from other implementations. That flaw can let attackers hide or reveal archive members unexpectedly and potentially smuggle files onto a victim filesystem during extraction. Together, the advisories underscore a broader supply-chain risk in Rust archive handling: malformed tar metadata and symlink processing can let malicious packages alter extracted contents in ways developers and automated tooling may not expect. Users are advised to upgrade to fixed releases and, where upgrades are not yet possible, audit registry content and block symlinks in published crates.
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.
Rust announced that Rust 1.96.0, scheduled for release on 2026-05-28, will fix CVE-2026-5223 by rejecting extraction of any symlink in crate tarballs. Users unable to upgrade were advised to audit registries for symlinks and configure registries to reject them where possible.
The Rust Security Response Team disclosed CVE-2026-5223, a medium-severity Cargo vulnerability affecting users of third-party registries. Cargo incorrectly handled symlinks in crate tarballs, allowing a malicious crate to overwrite another crate's cached source code from the same registry; crates.io users were not affected because symlinks are already forbidden there.
The Rust Security Response Team disclosed CVE-2026-5222, a low-severity Cargo vulnerability caused by incorrect normalization of third-party sparse registry URLs. Under narrow hosting conditions, the flaw could cause Cargo to send a victim's registry token to a malicious registry endpoint; the issue affects Cargo versions shipped from Rust 1.68 through 1.96.
A later GitHub advisory again documented the PAX header desynchronization issue in astral-tokio-tar and stated that the vulnerability is fixed in version 0.6.2 and later. No workaround other than upgrading was provided.
A GitHub security advisory disclosed a PAX header interpretation bug in astral-tokio-tar affecting versions before 0.6.2. The flaw could let attackers smuggle unexpected files during extraction by desynchronizing tar stream processing, and users were advised to upgrade.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
4 references tracked. Mallory keeps watching after this page renders.
blog.rust-lang.org
Open sourceblog.rust-lang.org
Open sourcegithub.com
Open sourcegithub.com
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.
A high-severity vulnerability, tracked as CVE-2025-62518 and codenamed TARmageddon, was discovered in the async-tar Rust library and its numerous forks, including tokio-tar, astral-tokio-tar, krata-tokio-tar, and others. The flaw, which carries a CVSS score of 8.1, allows for remote code execution (RCE) through file overwriting attacks, such as replacing configuration files or hijacking build backends. The vulnerability stems from inconsistent handling of PAX extended headers and ustar headers when determining file data boundaries, specifically when processing archives with PAX-extended headers containing size overrides. This parsing error enables attackers to smuggle additional archive entries by exploiting the mismatch, causing the parser to interpret file content as legitimate TAR headers. The async-tar library and its forks are widely used in critical tools and environments, including the uv Python package manager, testcontainers, and wasmCloud, amplifying the potential impact of the flaw. The most popular fork, tokio-tar, has over 5 million downloads on crates.io but is no longer maintained, increasing the risk as users may not receive timely patches. Edera, the security company that discovered the vulnerability in August 2025, highlighted the systemic risk posed by the open-source abandonware crisis, as the bug was inherited by a deep lineage of forks after the original project became unmaintained. Edera created and distributed patches for active forks, with astral-tokio-tar releasing version 0.5.6 to remediate the issue. However, users of unmaintained forks like tokio-tar are advised to migrate to patched alternatives such as astral-tokio-tar. The vulnerability's discovery underscores the challenges in tracking and patching security flaws in widely forked and abandoned open-source projects. The flaw's presence in foundational libraries for async archive processing in the Rust ecosystem means that build systems and production environments across many organizations could be at risk. Security experts warn that the lack of visibility into the use of these libraries further complicates mitigation efforts. The incident has reignited discussions about the need for better maintenance and oversight of critical open-source infrastructure. Organizations relying on affected libraries are urged to assess their exposure and implement available patches or migrate to maintained alternatives immediately. The coordinated disclosure and patching efforts by Edera aimed to minimize the window of exploitation before public announcement. This event highlights the importance of proactive vulnerability management and the risks associated with relying on unmaintained open-source components.
Jun 29, 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
A flaw in GNU tar 1.35 allows a crafted archive to show one set of contents during listing while extracting additional hidden files. The issue stems from a desynchronization between `tar -t` and `tar -x`: listing honors the size field for some non-data-bearing typeflags and skips data blocks, while extraction ignores that size and treats the same blocks as new headers. Researchers said the behavior affects symlink, character device, block device, and FIFO entries, but not directory entries, enabling hidden file injection with an archive reportedly smaller than 3 KB. The bug was disclosed on the GNU `bug-tar` and `oss-sec` mailing lists, where Red Hat was reported to have assigned **CVE-2026-5704**. A patch from GNU tar maintainer Paul Eggert was published to the GNU tar mailing list and committed to the upstream repository. Follow-up discussion on `oss-sec` also noted maintainer skepticism about parts of the original report and broader concerns about low-quality, possibly LLM-generated vulnerability submissions, but the technical issue and upstream fix were separately referenced in the disclosure and source commit.
Jun 29, 2026