# RUSTSEC-2026-0084: `logprinter` was removed from crates.io for malicious code

> A malicious Rust logging crate executed remote code via HTTP, requiring developers to remove the compromised dependency immediately.

- **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:** 9 Apr 2026

## What is RUSTSEC-2026-0084?

RUSTSEC-2026-0084 is a vulnerability in logprinter, published on 9 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The crate downloaded code from an external HTTP endpoint and executed it within its `trace()` fn.

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `logprinter` | crates.io | From 0.0.0-0 | None |

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

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

## Is RUSTSEC-2026-0084 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: RUSTSEC-2026-0084 is a vulnerability in logprinter, published on 9 Apr 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-0084 in the wild and no public exploit code.

Affected packages and fixed versions:
- logprinter (crates.io): affected from 0.0.0-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-0084/ (Markdown: https://insights.sbomify.com/RUSTSEC-2026-0084/index.md)
```

## Sources

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

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