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.

How does O3 Security protect against GHSA-6mw6-mj76-grwc?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-6mw6-mj76-grwc can be triaged on real exposure rather than presence alone.

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 12th 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

GHSA-6mw6-mj76-grwc — gix-date

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.

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

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 Sep 23, 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 CVEs12th percentile — riskier than 12% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

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`

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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-6mw6-mj76-grwc can be triaged on real exposure rather than presence alone.

Tailored to GHSA-6mw6-mj76-grwc. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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?

O3 Security finds GHSA-6mw6-mj76-grwc across crates.io dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works