Security readout for executives and security teams
Plain-English summary
A malicious release of the Rust arrayref package can run attacker-controlled code while software is being compiled. Organizations that built projects using version 0.3.10 may have exposed developer machines, CI systems, source code, credentials, and produced artifacts. Exposure requires investigation even if the resulting application was never deployed.
Executive priority
Treat confirmed compilation as an incident-response priority, not merely dependency maintenance. Immediately identify affected builds and protect CI credentials, signing keys, repositories, and deployment systems. If version 0.3.10 appears only in an inventory without evidence it was compiled, validate build history before declaring compromise.
Technical view
CVE-2026-77651 is a software supply-chain compromise affecting arrayref 0.3.10. The release contains a rogue dependency that registers with command-and-control infrastructure and enables arbitrary code execution during compilation. The supplied CVSS 3.1 score is 9.8, with potential confidentiality, integrity, and availability impact.
Likely exposure
Exposure is limited by the supplied record to projects that resolved and compiled arrayref version 0.3.10. Direct and transitive dependencies both matter. CI runners and developer workstations are the primary investigation targets, particularly where builds had network access or access to source repositories, signing material, deployment credentials, or other secrets.
Exploitation context
The malicious package behavior is established by the supplied sources, but the bundle does not establish how many downstream systems were compromised. The CVE is not listed as KEV. That does not prove exploitation is absent; it means active exploitation should not be claimed from the supplied evidence.
Researcher notes
The defining issue is build-time malicious behavior, categorized as CWE-506, rather than a conventional runtime flaw. Dependency resolution records and build-host evidence are therefore more informative than production application scanning alone. The supplied record names only version 0.3.10; broader affected-version claims, a specific safe version, victim prevalence, and active exploitation are not established here.
Mitigation direction
- Immediately block and remove arrayref 0.3.10 from dependency manifests, lockfiles, caches, and build pipelines.
- Isolate systems that compiled the affected version until investigation determines whether malicious code ran.
- Rebuild affected artifacts in clean environments using dependency versions confirmed safe by Rust or RustSec guidance.
- Rotate build credentials and secrets where telemetry indicates execution or possible exposure.
- Review Rust and RustSec advisories for updates; the supplied evidence does not identify a specific patched version.
Validation and detection
- Search dependency manifests, Cargo.lock files, SBOMs, and artifact provenance for exact version 0.3.10.
- Review CI and developer build histories to identify where and when version 0.3.10 was compiled.
- Examine build-host network telemetry for unexpected command-and-control registration during affected compilation periods.
- Review endpoint telemetry for unexplained processes, file changes, credential access, or persistence during those periods.
- Confirm clean rebuilds no longer resolve version 0.3.10 and produce expected dependency inventories.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-506: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-77651 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9mitreVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://blog.rust-lang.org/2026/08/20/supply-chain-attack-on-arrayrefCVE reference, mitre
- https://github.com/rustsec/advisory-db/issues/3161CVE reference, mitre
- https://www.stepsecurity.io/blog/arrayref-rust-crate-supply-chain-attackCVE reference, mitre
- https://safedep.io/arrayref-proc-macro1-rust-build-time-malware/CVE reference, mitre
- https://rustsec.org/advisories/RUSTSEC-2026-0260.htmlCVE reference, mitre
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Embedded Malicious Code
Embedded Malicious Code represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.