# RUSTSEC-2026-0175: `onering` 1.4.1 was removed from crates.io for malicious code

> A malicious version of the onering Rust crate attempted to exfiltrate project metadata and code, requiring developers to avoid 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:** Yes
- **Published:** 10 Jun 2026

## What is RUSTSEC-2026-0175?

RUSTSEC-2026-0175 is a vulnerability in onering, published on 10 Jun 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 `onering` crate was published with code that attempted to
exfiltrate both metadata and code from the project it was included within.

One malicious version was published on 2026-06-10, approximately six hours
before removal. This crate has no dependencies on crates.io, and there is no
evidence of actual usage of the compromised version.

Thanks to Charlie Eriksen for the report.

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `onering` | crates.io | From 1.4.1 | 1.4.2-0 |

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

Upgrade onering to 1.4.2-0 or later.

## Is RUSTSEC-2026-0175 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: RUSTSEC-2026-0175 is a vulnerability in onering, published on 10 Jun 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-0175 in the wild and no public exploit code.

Affected packages and fixed versions:
- onering (crates.io): affected from 1.4.1; fixed in 1.4.2-0

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-0175/ (Markdown: https://insights.sbomify.com/RUSTSEC-2026-0175/index.md)
```

## Sources

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

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