Rust advisories / time_calibrator
Vulnerability CriticalRUSTSEC-2026-0030 · time_calibrator
RUSTSEC-2026-0030: `time_calibrator` was removed from crates.io due to malicious code
Short answerA security vulnerability in the time_calibrator crate: `time_calibrator` was removed from crates.io due to malicious code. GitHub rates it Critical. No fixed version: replace the crate or remove the affected code path.
| Crate | time_calibrator |
|---|---|
| Type | Vulnerability (malicious) |
| Affected versions | Every version. |
| Fixed in | none |
| Severity | Critical (GitHub rating) |
| Published | 2026-03-03 |
| Last changed | 2026-03-17 |
| Also known as | GHSA-77xj-rrh3-wx3v |
What to do
- Find who pulls it in:
cargo tree -i time_calibrator. - Avoid the affected API, or replace the crate.
Details from the advisory
It was reported time_calibrator contained malicious code, that would try to upload .env files to a server.
The malicious crate had only 1 version published at 2026-02-28 and no evidence of actual usage. The crate was removed from crates.io and the user account was locked. There were no crates depending on this crate on crates.io.
Thanks to Gabriel Silva for finding and reporting this to the Rust security response working group, and thanks to Emily Albini for co-ordinating with the crates.io and infra-admin teams.
References
From the RustSec Advisory Database (CC0-1.0) via the OSV export, downloaded Oct 24, 2026. Severity score computed from the published CVSS vector.
Up next
Are you affected?Check your whole dependency treePaste Cargo.lock: every advisory, for your exact versions.Read it next →Also worth your time
Did this answer your question?