The internment crate 0.8.7 for Rust can trigger execution of malicious code when compiling a project that uses the crate, because it has a rogue dependency that registers with a command-and-control server to offer arbitrary code execution.
CVE-2026-77649
Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-21. a secondary CVSS source baseline 9.8; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.8
- EG Score
- 9.8(high)
- EG Risk
- 49(Track)EG Risk 49/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity98% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
August 21, 2026
Last Modified
August 21, 2026
Advisory Details (5)
Auto-updated Aug 21, 2026Rust Supply-Chain Attack: arrayref, internment, and append-only-vec Poisoned by the proc-macro1 Build-Time Dropper - StepSecurity
https://www.stepsecurity.io/blog/arrayref-rust-crate-supply-chain-attackMalicious Rust Crate arrayref Runs a Build-Time Payload - Real-time Open Source Software Supply Chain Security
https://safedep.io/arrayref-proc-macro1-rust-build-time-malware/RUSTSEC-2026-0266: internment: `internment` 0.8.7 was removed from crates.io due to a malicious dependency › RustSec Advisory Database
https://rustsec.org/advisories/RUSTSEC-2026-0266.htmlMalware: `arrayref` 0.3.10 executes a remote payload at build time via typosquatted `proc-macro1` · Issue #3161 · rustsec/advisory-db · GitHub
https://github.com/rustsec/advisory-db/issues/3161Supply chain attack on arrayref | Rust Blog
https://blog.rust-lang.org/2026/08/20/supply-chain-attack-on-arrayrefVendor Advisories for CVE-2026-77649(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 6× in last 7d / 6× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-21 08:58 UTCGHSA enrichment
- 2026-08-21 05:14 UTCEG score recompute
- 2026-08-21 05:14 UTCGHSA enrichment
- 2026-08-21 01:30 UTCEG score recompute
- 2026-08-21 00:51 UTCEG score recompute
- 2026-08-21 00:51 UTCMITRE cvelistV5first tracked
Frequently asked(4)
What is CVE-2026-77649?
When was CVE-2026-77649 disclosed?
What is the CVSS score of CVE-2026-77649?
How do I remediate CVE-2026-77649?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-77649
Is Your Infrastructure Affected by CVE-2026-77649?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.