Skip to content
Fencer Intel
no cvss —

RUSTSEC-2026-0171 json

`logflux` was removed from crates.io for malicious code

published 5mo ago modified 5mo 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

The `logflux` crate attempted to download and run a malicious payload on the user's machine.

The malicious crate had 1 version published on 2026-04-26, approximately 1 month before removal, and had no evidence of actual usage. This crate had no dependencies on crates.io.

Thanks to Paweł Bis for discovering and reporting this crate!

This appears to have been part of a campaign targeting people applying for Rust jobs. Please be careful with take-home assignments, especially if they ask you to use specific dependencies.

Is RUSTSEC-2026-0171 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 Fencer

Affected packages

ecosystem package affected fixed in
crates.io logflux
>=0.0.0-0
 no fix listed

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.