RUSTSEC-2026-0262 json
`append-only-vec` 0.1.9 was removed from crates.io due to a malicious dependency
published 2mo ago modified 22d ago
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
A new version of the `append-only-vec` crate was published with a direct dependency on `proc-macro1`, which would execute a malicious build script.
The compromised version of this crate was published on 2026-08-20, and was removed approximately 107 minutes later.
The compromised crate version was used as part of a malware campaign targeted at users of `arrayref`, which was downloaded 2,285 times before being removed; see [the `arrayref` advisory][arrayref-advisory] for more detail.
[arrayref-advisory]: https://rustsec.org/advisories/RUSTSEC-2026-0260.html
Patch / fix
- crates.io append-only-vec 0.1.10-0
Is RUSTSEC-2026-0262 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerAffected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| crates.io | append-only-vec | >=0.1.9, <0.1.10-0 |
0.1.10-0 |
References
Sources
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.