Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 5.5

gix-date can create non-utf8 string with TimeBuf::as_str

CVE-2026-0810GHSA-6mw6-mj76-grwc

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (gix-date 0.12.0), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • crates.io gix-date

    Affected
    < 0.12.0
    Fixed in
    0.12.0

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
5.5 · CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N/E:P · score source
EPSS
  • CVE-2026-0810: 0.21% estimated exploitation activity in the next 30 days; percentile 11.40 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

The function gixdate::parse::TimeBuf::asstr 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::fromutf8 to the function TimeBuf::write.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-6mw6-mj76-grwc

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-0810

Advisory: gix-date can create non-utf8 string with `TimeBuf::as_str`
IDs: CVE-2026-0810, GHSA-6mw6-mj76-grwc
Record: https://patchnext.com/advisories/cve-2026-0810 (revision 1, source checked 26 Oct 2026, 15:39 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: gix-date 0.12.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io gix-date: affected < 0.12.0; fixed in 0.12.0

## Suggested inspection (read-only)
- crates.io gix-date: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on gix-date.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-6mw6-mj76-grwc (GitHub-reviewed advisory GHSA-6mw6-mj76-grwc lists affected ranges: crates.io gix-date >=0 <0.12.0)

Commands are suggestions: review each one before running it.

Loading voting…