Rust advisories / gix-date
Vulnerability MediumRUSTSEC-2025-0140 · gix-date
RUSTSEC-2025-0140: Non-utf8 String can be created with `TimeBuf::as_str`
Short answerA security vulnerability in the gix-date crate: Non-utf8 String can be created with `TimeBuf::as_str`. GitHub rates it Medium. Fixed in 0.12.0: update to a fixed version.
| Crate | gix-date |
|---|---|
| Type | Vulnerability (memory-corruption) |
| Affected versions | Before 0.12.0. |
| Fixed in | 0.12.0 |
| Severity | Medium (GitHub rating) |
| Published | 2025-12-29 |
| Last changed | 2026-03-04 |
| Also known as | CVE-2026-0810, GHSA-6mw6-mj76-grwc |
| Affected functions | gix_date::parse::TimeBuf::as_str |
What to do
- See which version you have:
cargo tree -i gix-date(it also shows which of your dependencies pulls it in). - Update within your version requirement:
cargo update -p gix-date. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for examplegix-date = "0.12.0") or update the dependency that pulls it in. - Check again with
cargo audit, or paste your Cargo.lock into our Cargo.toml checker.
Details from the advisory
The function gix_date::parse::TimeBuf::as_str can create an illegal string containing non-utf8 characters. This violates the safety invariant of TimeBuf and can lead to undefined behavior when consuming the string.
The bug can be prevented by adding str::from_utf8 to the function TimeBuf::write.
References
- Package: crates.io/crates/gix-date
- Advisory: rustsec.org/advisories/RUSTSEC-2025-0140.html
- Report: github.com/GitoxideLabs/gitoxide/issues/2305
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?