gix-date can create non-utf8 string with `TimeBuf::as_str`
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`.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2026-0810US | — | — | ||
A flaw was found in gix-date. The `gix_date::parse::TimeBuf::as_str` function can generate strings containing invalid non-UTF8 characters. This issue violates the internal safety i… | ||||
02
references
External citations — patches, advisories, analysis.
- https://access.redhat.com/security/cve/CVE-2026-0810WEB
- https://bugzilla.redhat.com/show_bug.cgi?id=2427057WEB
- https://github.com/GitoxideLabs/gitoxidePACKAGE
- https://github.com/GitoxideLabs/gitoxide/commit/76376ef5e97c63e108db0c9fe2eb096f4bfe70f7WEB
- https://github.com/GitoxideLabs/gitoxide/issues/2305WEB
- https://github.com/GitoxideLabs/gitoxide/pull/2306WEB
- https://nvd.nist.gov/vuln/detail/CVE-2026-0810ADVISORY
- https://rustsec.org/advisories/RUSTSEC-2025-0140.htmlWEB
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan