Build-time code execution via malicious dependency
Published Aug 21, 2026 · Updated Aug 21, 2026
Malicious dependency injection in arrayref 0.3.10 allows remote attackers to execute code when Cargo compiles an affected project. The release's Cargo.toml adds proc-macro1 1.0.107, whose build.rs downloads and launches an architecture-specific binary. A Cargo build that resolves 0.3.10 is sufficient; the payload runs with the developer or CI runner's privileges on Unix or Windows hosts.
Summary
What happened
Malicious dependency injection in arrayref 0.3.10 allows remote attackers to execute code when Cargo compiles an affected project. The release's Cargo.toml adds proc-macro1 1.0.107, whose build.rs downloads and launches an architecture-specific binary. A Cargo build that resolves 0.3.10 is sufficient; the payload runs with the developer or CI runner's privileges on Unix or Windows hosts.
The record
- CVE
- CVE-2026-77651
- Published
- Aug 21, 2026
- Updated
- Aug 21, 2026
- Vendor
- David Roundy
- Product
- arrayref
- Classifications
- CWE-506, T1195.001, T1105
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 20, 2026Exploitation reportedCrates.io arrayref supply-chain attack
- Aug 21, 2026CVE publishedPublication date reported by the CVE source.
- Aug 21, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0.3.10
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Reported exploitation
- Crates.io arrayref supply-chain attackexploit chain
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo