Skip to content
Fencer Intel
no cvss —

RUSTSEC-2026-0175 json

`onering` 1.4.1 was removed from crates.io for malicious code

published 5mo ago modified last mo.

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 `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.

Patch / fix

  • crates.io onering 1.4.2-0

Is RUSTSEC-2026-0175 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 onering
>=1.4.1, <1.4.2-0
1.4.2-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.