Skip to content
Applications

CVE-2026-77651

9.8
Critical
EPSS 0.45%Patch availableAug 22, 2026

Malicious Rust crate dependency enables arbitrary code execution during compilation.

common questions

Is CVE-2026-77651 being exploited?

Not confirmed. CVE-2026-77651 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.45% probability of exploitation in the next 30 days.

How severe is CVE-2026-77651?

CVE-2026-77651 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-77651?

Yes. A fix has been recorded for CVE-2026-77651. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-77651 affect?

CVE-2026-77651 affects Rust projects using arrayref 0.3.10, Developer workstations, CI/CD build runners, Artifact repositories. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-77651?

Stop builds using arrayref 0.3.10, remove/update dependency, audit builds and rotate secrets.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Rust projects using arrayref 0.3.10Developer workstationsCI/CD build runnersArtifact repositories
impact

Compiling projects with arrayref 0.3.10 can run attacker-controlled code via a rogue dependency, compromising developer machines, CI/CD, and secrets.

action required

Immediate action required

affected versions
droundy arrayref
  • affected0.3.10

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free