Which versions of time_calibrator are affected by GHSA-77XJ-RRH3-WX3V?

time_calibrator (rust) versions >= 0 is affected.

Is there a fix for GHSA-77XJ-RRH3-WX3V?

No fixed version is listed for GHSA-77XJ-RRH3-WX3V yet. Monitor the advisory for updates and apply mitigations in the interim.

Is GHSA-77XJ-RRH3-WX3V exploitable, and should I be worried?

Whether GHSA-77XJ-RRH3-WX3V is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether GHSA-77XJ-RRH3-WX3V is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

GHSA-77XJ-RRH3-WX3V in time_calibrator

GHSA-77XJ-RRH3-WX3V

GHSA-77XJ-RRH3-WX3V is a critical-severity security vulnerability in time_calibrator (rust), affecting versions >= 0. No fixed version is listed yet.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!

Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

time_calibrator was removed from crates.io due to malicious code

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.

Rust security response working group thanks Gabriel Silva for finding and reporting this, and thanks to Emily Albini for co-ordinating with the crates.io and infra-admin teams.

Impact

Affected versions

time_calibrator (>= 0)

Security releases

Not available

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

No fixed version is listed for GHSA-77XJ-RRH3-WX3V yet.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is GHSA-77XJ-RRH3-WX3V? GHSA-77XJ-RRH3-WX3V is a critical-severity security vulnerability in time_calibrator (rust), affecting versions >= 0. No fixed version is listed yet.
Which versions of time_calibrator are affected by GHSA-77XJ-RRH3-WX3V? time_calibrator (rust) versions >= 0 is affected.
Is there a fix for GHSA-77XJ-RRH3-WX3V? No fixed version is listed for GHSA-77XJ-RRH3-WX3V yet. Monitor the advisory for updates and apply mitigations in the interim.
Is GHSA-77XJ-RRH3-WX3V exploitable, and should I be worried? Whether GHSA-77XJ-RRH3-WX3V is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether GHSA-77XJ-RRH3-WX3V is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.