# RUSTSEC-2026-0260: `arrayref` 0.3.10 was removed from crates.io due to a malicious dependency

> A malicious version of the arrayref Rust crate executed arbitrary code during build, requiring developers to ensure they do not use the compromised release.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Aug 2026

## What is RUSTSEC-2026-0260?

RUSTSEC-2026-0260 is a vulnerability in arrayref, published on 20 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A new version of the `arrayref` crate was published with a direct dependency
on `proc-macro1`, which would execute a malicious build script.

This compromised version was published on 2026-08-20 and removed approximately
86 minutes later. It was downloaded 2,285 times, which constituted less than
10% of `arrayref` download traffic across all versions, as most users had older
versions of `arrayref` in their lockfiles.

## Which versions are affected by RUSTSEC-2026-0260?

1 open source package ship an affected version, including arrayref.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `arrayref` | crates.io | From 0.3.10-0 | None |

## How do I fix RUSTSEC-2026-0260?

No fix has been published for RUSTSEC-2026-0260 yet. Limit exposure of the affected software until one is available.

## Is RUSTSEC-2026-0260 being exploited?

There is no known exploitation of RUSTSEC-2026-0260 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for RUSTSEC-2026-0260 and fix it if it is affected.

What it is: RUSTSEC-2026-0260 is a vulnerability in arrayref, published on 20 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of RUSTSEC-2026-0260 in the wild and no public exploit code.

Affected packages and fixed versions:
- arrayref (crates.io): affected from 0.3.10-0; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/RUSTSEC-2026-0260/ (Markdown: https://insights.sbomify.com/RUSTSEC-2026-0260/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/RUSTSEC-2026-0260

---
From sbomify Insights: https://insights.sbomify.com/RUSTSEC-2026-0260/
Summaries are generated and may contain mistakes; the official description above is the record.