CVE-2026-77651

9.8

droundy · arrayref

The arrayref crate 0.3.10 for Rust contains malicious code that executes during project compilation by communicating with a command and control server to facilitate arbitrary code execution.

Executive summary

The droundy arrayref crate version 0.3.10 is affected by an embedded malicious code vulnerability that enables supply chain attacks during the software build process.

Vulnerability

This is an embedded malicious code vulnerability (CWE-506) where the crate includes a rogue dependency that registers with a remote command and control server. The attack is unauthenticated and triggered automatically during the compilation phase of any project utilizing this version.

Business impact

The inclusion of malicious code in a build dependency poses a severe risk to the software supply chain. A successful exploit allows an attacker to achieve arbitrary code execution on developer machines or CI/CD pipelines, potentially leading to the injection of backdoors into downstream products, intellectual property theft, and total compromise of development environments. The CVSS score of 9.8 reflects the critical nature of this supply chain compromise.

Remediation

Immediate Action: Developers must immediately remove or update the droundy arrayref crate to a secure version and audit all build environments for signs of unauthorized network communication or file system changes.

Proactive Monitoring: Monitor build pipelines and developer workstations for unexpected outbound network connections to unknown IP addresses during the compilation phase.

Compensating Controls: Implement supply chain security tools that perform dependency scanning and static analysis on third party crates to detect malicious patterns before they are integrated into build processes.

Exploitation status

Public Exploit Available: Unknown.

Analyst recommendation

Given the critical severity of this supply chain vulnerability, all users of the arrayref crate must verify their project dependencies immediately. Organizations should prioritize updating to a clean version and conducting a forensic review of build systems that have utilized version 0.3.10 to ensure no persistent unauthorized access has been established.

More droundy CVEs