Build-time arbitrary code execution in Rust arrayref 0.3.10
CVE-2026-77651 is a supply-chain compromise affecting version 0.3.10 of the Rust crate arrayref. An attacker compromised a maintainer account and published a malicious release introducing the rogue proc-macro1 dependency. Compiling a project that resolves the affected release can execute malicious build-time code that registers with a command-and-control server and enables arbitrary code execution. Exploitation does not require running the compiled application. The malicious release was published and removed from crates.io on August 20, 2026.
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
Successful exploitation can compromise developer workstations and CI/CD workers with the permissions available to the build process. Arbitrary code execution can expose build-accessible source code, credentials, and other sensitive data; permit modification of build artifacts and workspace contents; and disrupt build infrastructure. The vulnerability is rated Critical with a CVSS v3.1 score of 9.8 and high confidentiality, integrity, and availability impacts.
If you can’t patch tonight, do this now.
Block arrayref 0.3.10 from dependency resolution and build pipelines, including transitive dependency paths. Prevent retrieval or compilation of the affected release and review dependency changes for the rogue proc-macro1 package. Restrict build-environment outbound connectivity to limit command-and-control communication, although this does not prevent malicious build-time code from executing.
Patch, then assume compromise.
Replace arrayref 0.3.10 with a verified known-safe release; the recommended rollback is version 0.3.9 or an earlier known-safe version. Update dependency constraints and lockfiles to exclude the malicious release, purge affected cached packages from developer and CI environments, and rebuild only after verifying the resolved dependency graph. Review automated builds during the August 20, 2026 publication window and any subsequent builds using cached copies to determine whether the malicious dependency executed.
No public exploits tracked yet. Mallory keeps watching.
10 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.