How severe is GHSA-6mw6-mj76-grwc?

No CVSS score has been assigned to GHSA-6mw6-mj76-grwc yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-6mw6-mj76-grwc?

GHSA-6mw6-mj76-grwc affects the following packages: gix-date (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-6mw6-mj76-grwc?

Update gix-date to 0.12.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6mw6-mj76-grwc is resolved across your whole dependency graph.

How do I detect GHSA-6mw6-mj76-grwc in my crates.io dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for gix-date, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-6mw6-mj76-grwc if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-6mw6-mj76-grwc actively exploited in the wild?

No public exploit code has been indexed for GHSA-6mw6-mj76-grwc yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-6mw6-mj76-grwc?

GHSA-6mw6-mj76-grwc has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 11th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-6mw6-mj76-grwc?

GHSA-6mw6-mj76-grwc is classified as CWE-135 (CWE-135), CWE-682 (CWE-682). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-6mw6-mj76-grwc published, and has it been updated?

GHSA-6mw6-mj76-grwc was published on January 5, 2026 and was last updated on September 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🦀 crates.io

Not in CISA KEV

gix-date can create non-utf8 string with `TimeBuf::as_str`GHSA-6mw6-mj76-grwc

Fix: GitoxideLabs/gitoxide#2306

GHSA-6mw6-mj76-grwc is a CWE-135 vulnerability in gix-date. A fix is available for gix-date — see the affected versions and patch details below.

Also known asCVE-2026-0810RUSTSEC-2025-0140

Published

Jan 5, 2026

Updated

Sep 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 11, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA’s SSVC triage for GHSA-6mw6-mj76-grwc.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs11th percentile — riskier than 11% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🦀gix-date

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`gix-date`	all versions	0.12.0`cargo update -p gix-date --precise 0.12.0`

Affected Products

1 product · 1 configurations

Application

gix-dategitoxidelabs

< 0.12.0

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for gix-date, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update gix-date to 0.12.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6mw6-mj76-grwc is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

This vulnerability is rated Moderate for Red Hat products. A flaw in the `gix-date` library can generate invalid non-UTF8 strings, leading to undefined behavior when processed. The most likely impact from a successful attack is to data integrity, by the malicious data being able to corrupt data being hold in memory…

Workaround published by Red Hat

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

Source: Red Hat security advisory for GHSA-6mw6-mj76-grwc (CC BY 4.0)

Frequently Asked Questions

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`.

O3 Security · Impact-Aware SCA

Is GHSA-6mw6-mj76-grwc in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works