What is CVE-2026-0810?

CVE-2026-0810 is a medium-severity out-of-bounds write vulnerability in gix-date (rust), affecting versions < 0.12.0. It is fixed in 0.12.0. A write operation targets a memory location beyond the intended buffer boundary.

Which versions of gix-date are affected by CVE-2026-0810?

gix-date (rust) versions < 0.12.0 is affected.

Is there a fix for CVE-2026-0810?

Yes. CVE-2026-0810 is fixed in 0.12.0. Upgrade to this version or later.

Is CVE-2026-0810 exploitable, and should I be worried?

Whether CVE-2026-0810 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2026-0810 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2026-0810 in gix-date

Q: Which versions of gix-date are affected by CVE-2026-0810?

gix-date (rust) versions < 0.12.0 is affected.

Q: Is there a fix for CVE-2026-0810?

Yes. CVE-2026-0810 is fixed in 0.12.0. Upgrade to this version or later.

Q: Is CVE-2026-0810 exploitable, and should I be worried?

Whether CVE-2026-0810 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2026-0810 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2026-0810?

Upgrade gix-date to 0.12.0 or later.

CVE-2026-0810

CVE-2026-0810 is a medium-severity out-of-bounds write vulnerability in gix-date (rust), affecting versions < 0.12.0. It is fixed in 0.12.0.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!

Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

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.

Impact

A write operation targets a memory location beyond the intended buffer boundary. Typical impact: memory corruption, crash, or arbitrary code execution.

Affected versions

gix-date (< 0.12.0)

Security releases

gix-date → 0.12.0 (rust)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade gix-date to 0.12.0 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2026-0810? CVE-2026-0810 is a medium-severity out-of-bounds write vulnerability in gix-date (rust), affecting versions < 0.12.0. It is fixed in 0.12.0. A write operation targets a memory location beyond the intended buffer boundary.
Which versions of gix-date are affected by CVE-2026-0810? gix-date (rust) versions < 0.12.0 is affected.
Is there a fix for CVE-2026-0810? Yes. CVE-2026-0810 is fixed in 0.12.0. Upgrade to this version or later.
Is CVE-2026-0810 exploitable, and should I be worried? Whether CVE-2026-0810 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2026-0810 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2026-0810? Upgrade gix-date to 0.12.0 or later.