# CVE-2026-0810: Gix-date: gix-date: undefined behavior due to invalid string generation

> Attackers can trigger undefined behavior and potential application instability by causing the gix-date library to generate invalid non-UTF8 strings during date parsing.

- **Severity:** High 7.1 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Jan 2026
- **Updated:** 20 Apr 2026
- **Also known as:** DEBIAN-CVE-2026-0810, GHSA-6mw6-mj76-grwc, MINI-5587-4334-wv9c, RUSTSEC-2025-0140, UBUNTU-CVE-2026-0810

## What is CVE-2026-0810?

CVE-2026-0810 is a high-severity vulnerability in GitoxideLabs Logging Subsystem for Red Hat OpenShift, published on 26 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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 invariants of the `TimeBuf` component, leading to undefined behavior when these malformed strings are subsequently processed. This could potentially result in application instability or other unforeseen consequences.

Weakness: CWE-682 (Incorrect Calculation), CWE-135 (Incorrect Calculation of Multi-Byte String Length)

## Which versions are affected by CVE-2026-0810?

3 open source packages ship an affected version, including gix-date. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `gix-date` | crates.io | All versions | 0.12.0 |
| `gix-date` | crates.io | All versions | 0.12.0 |
| `gix-date` | crates.io | From 0.0.0-0 | 0.12.0 |

Products: Gitoxidelabs Gix-Date.

## How do I fix CVE-2026-0810?

Upgrade gix-date to 0.12.0 or later.

## Is CVE-2026-0810 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-0810 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-0810 and fix it if it is affected.

What it is: CVE-2026-0810 is a high-severity vulnerability in GitoxideLabs Logging Subsystem for Red Hat OpenShift, published on 26 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-0810 exists.

Affected packages and fixed versions:
- gix-date (crates.io): affected all versions; fixed in 0.12.0
- gix-date (crates.io): affected all versions; fixed in 0.12.0
- gix-date (crates.io): affected from 0.0.0-0; fixed in 0.12.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-0810/ (Markdown: https://insights.sbomify.com/CVE-2026-0810/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-0810
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-0810
- OSV: https://osv.dev/vulnerability/CVE-2026-0810

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-0810/
Summaries are generated and may contain mistakes; the official description above is the record.