How severe is GHSA-77xj-rrh3-wx3v?

No CVSS score has been assigned to GHSA-77xj-rrh3-wx3v yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-77xj-rrh3-wx3v?

GHSA-77xj-rrh3-wx3v affects the following packages: time_calibrator (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-77xj-rrh3-wx3v?

The records we use list no patched version of time_calibrator for GHSA-77xj-rrh3-wx3v. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

How do I detect GHSA-77xj-rrh3-wx3v in my crates.io dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for time_calibrator, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-77xj-rrh3-wx3v if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-77xj-rrh3-wx3v actively exploited in the wild?

No public exploit code has been indexed for GHSA-77xj-rrh3-wx3v yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-77xj-rrh3-wx3v published, and has it been updated?

GHSA-77xj-rrh3-wx3v was published on March 4, 2026 and was last updated on March 5, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🦀 crates.io

Not in CISA KEV

`time_calibrator` was removed from crates.io due to malicious codeGHSA-77xj-rrh3-wx3v

GHSA-77xj-rrh3-wx3v is a security vulnerability in time_calibrator. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

Also known asRUSTSEC-2026-0030

Published

Mar 4, 2026

Updated

Mar 5, 2026

Affected

1 pkg

Patched

None yet

Exploits

None indexed

Exploitation data as of Mar 5, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🦀time_calibrator

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`time_calibrator`	all versions	No fix

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for time_calibrator, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of time_calibrator for GHSA-77xj-rrh3-wx3v. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is GHSA-77xj-rrh3-wx3v in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works