How severe is GHSA-wf45-3gpw-vrqv?

No CVSS score has been assigned to GHSA-wf45-3gpw-vrqv yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-wf45-3gpw-vrqv?

GHSA-wf45-3gpw-vrqv affects the following packages: time_calibrators (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-wf45-3gpw-vrqv?

The records we use list no patched version of time_calibrators for GHSA-wf45-3gpw-vrqv. 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-wf45-3gpw-vrqv in my crates.io dependencies?

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

How do I mitigate GHSA-wf45-3gpw-vrqv 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-wf45-3gpw-vrqv actively exploited in the wild?

No public exploit code has been indexed for GHSA-wf45-3gpw-vrqv 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-wf45-3gpw-vrqv published, and has it been updated?

GHSA-wf45-3gpw-vrqv 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_calibrators` was removed from crates.io due to malicious codeGHSA-wf45-3gpw-vrqv

GHSA-wf45-3gpw-vrqv is a security vulnerability in time_calibrators. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

Also known asRUSTSEC-2026-0031

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_calibrators

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

The time_calibrators crate attempted to exfiltrate .env files to a server that was in turn impersonating the legitimate timeapi.io service.

The malicious crate had 1 version published on 2026-03-03 approximately 3 hours before removal and had no evidence of actual downloads. There were no crates depending on this crate on crates.io.

Rust security response working group thanks cybergeek for finding and reporting this, and thanks to Emily Albini for co-ordinating with the crates.io team.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`time_calibrators`	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_calibrators, 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_calibrators for GHSA-wf45-3gpw-vrqv. 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

The `time_calibrators` crate attempted to exfiltrate `.env` files to a server that was in turn impersonating the legitimate `timeapi.io` service. The malicious crate had 1 version published on 2026-03-03 approximately 3 hours before removal and had no evidence of actual downloads. There were no crates depending on this crate on crates.io. Rust security response working group thanks cybergeek for finding and reporting this, and thanks to Emily Albini for co-ordinating with the crates.io team.

O3 Security · Impact-Aware SCA

Is GHSA-wf45-3gpw-vrqv in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works