CVE-2026-0810

HIGHNVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.1 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 91% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
7.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.1Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.1
EG Score
7.1(medium)
EG Risk
48(Track*)
EG Risk 48/100SSVC: Track*

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity71% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
0%
EPSS %ILE
10%
KEV
Not listed

Published

January 26, 2026

Last Modified

June 17, 2026

Advisory Details (5)

Auto-updated Aug 6, 2026
Patch available. Sources: redhat.
generic

Non-utf8 String can be created with `TimeBuf::as_str` · Issue #2305 · GitoxideLabs/gitoxide · GitHub

https://github.com/GitoxideLabs/gitoxide/issues/2305
generic

RUSTSEC-2025-0140: gix-date: Non-utf8 String can be created with `TimeBuf::as_str` › RustSec Advisory Database

https://rustsec.org/advisories/RUSTSEC-2025-0140.html
generic

crates.io: Rust Package Registry

https://crates.io/crates/gix-date
redhat Patch Available

2427057 – (CVE-2026-0810, RUSTSEC-2025-0140) CVE-2026-0810 gix-date: gix-date: Undefined behavior due to invalid string generation

https://bugzilla.redhat.com/show_bug.cgi?id=2427057
redhat Patch Available

CVE-2026-0810 - Red Hat Customer Portal

Affected: Red Hat Enterprise Linux 8 or OpenShift Container Platform 4, is affected by this vulnerability and a fix may be released to a

https://access.redhat.com/security/cve/CVE-2026-0810

Affected Packages

(3 across 3 ecosystems)
crates.io(1)
PackageVulnerable rangeFixed inDependents
gix-date—0.12.0—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
rust-gix-date0.10.7-1, 0.15.3-1, 0.15.6-1, 0.9.3-1, 0.9.3-2——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
rust-gix-date0.10.7-1, 0.15.3-1, 0.15.6-1, 0.9.3-1, 0.9.3-2——

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 4× in last 7d / 22× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 135 total refreshes for this CVE.

  1. 2026-09-18 19:27 UTCEPSS rescore
  2. 2026-09-16 05:14 UTCEPSS rescore
  3. 2026-09-13 16:46 UTCEPSS rescore
  4. 2026-09-12 15:00 UTCEPSS rescore
  5. 2026-09-11 14:52 UTCEPSS rescore
  6. 2026-09-11 09:36 UTCEPSS rescore
  7. 2026-09-10 09:34 UTCEPSS rescore
  8. 2026-09-08 22:00 UTCEPSS rescore
  9. 2026-09-07 16:01 UTCEPSS rescore
  10. 2026-09-06 13:47 UTCEPSS rescore
  11. 2026-09-04 05:06 UTCEPSS rescore
  12. 2026-09-02 14:11 UTCEPSS rescore
  13. 2026-09-01 13:53 UTCEPSS rescore
  14. 2026-09-01 01:04 UTCOSV refresh
  15. 2026-08-30 19:17 UTCEPSS rescore
  16. 2026-08-30 01:21 UTCEPSS rescore
  17. 2026-08-28 21:40 UTCEPSS rescore
  18. 2026-08-27 14:24 UTCEPSS rescore
  19. 2026-08-25 13:48 UTCEPSS rescore
  20. 2026-08-23 00:19 UTCEPSS rescore
  21. 2026-08-21 23:48 UTCEPSS rescore
  22. 2026-08-20 22:55 UTCEPSS rescore
  23. 2026-08-19 17:03 UTCEPSS rescore
  24. 2026-08-18 13:48 UTCEPSS rescore
  25. 2026-08-16 14:56 UTCEPSS rescore
Show 75 more
  1. 2026-08-16 02:14 UTCEPSS rescore
  2. 2026-08-15 01:30 UTCEPSS rescore
  3. 2026-08-14 12:16 UTCEG score recompute
  4. 2026-08-13 22:00 UTCEPSS rescore
  5. 2026-08-13 04:28 UTCEG score recompute
  6. 2026-08-12 13:50 UTCEPSS rescore
  7. 2026-08-11 13:42 UTCEPSS rescore
  8. 2026-08-10 23:59 UTCEPSS rescore
  9. 2026-08-09 18:16 UTCEG score recompute
  10. 2026-08-09 13:46 UTCEPSS rescore
  11. 2026-08-08 16:37 UTCEPSS rescore
  12. 2026-08-07 23:30 UTCEG score recompute
  13. 2026-08-06 13:46 UTCEPSS rescore
  14. 2026-08-06 04:56 UTCEG score recompute
  15. 2026-08-05 19:17 UTCEPSS rescore
  16. 2026-08-04 15:09 UTCEPSS rescore
  17. 2026-08-04 10:38 UTCEPSS rescore
  18. 2026-08-03 10:35 UTCEPSS rescore
  19. 2026-08-02 22:06 UTCEG score recompute
  20. 2026-08-02 02:26 UTCEPSS rescore
  21. 2026-08-01 04:15 UTCEPSS rescore
  22. 2026-07-31 06:42 UTCOSV refresh
  23. 2026-07-30 16:27 UTCEPSS rescore
  24. 2026-07-30 01:30 UTCEPSS rescore
  25. 2026-07-28 15:36 UTCEPSS rescore
  26. 2026-07-27 14:13 UTCEPSS rescore
  27. 2026-07-26 14:54 UTCEPSS rescore
  28. 2026-07-26 14:54 UTCEPSS rescore
  29. 2026-07-25 14:17 UTCEPSS rescore
  30. 2026-07-24 14:17 UTCEPSS rescore
  31. 2026-07-23 14:18 UTCEPSS rescore
  32. 2026-07-23 03:04 UTCEG score recompute
  33. 2026-07-22 14:08 UTCEPSS rescore
  34. 2026-07-21 15:24 UTCEPSS rescore
  35. 2026-07-20 17:08 UTCEPSS rescore
  36. 2026-07-19 14:30 UTCEPSS rescore
  37. 2026-07-19 02:28 UTCEPSS rescore
  38. 2026-07-18 10:04 UTCEPSS rescore
  39. 2026-07-16 17:02 UTCEPSS rescore
  40. 2026-07-15 16:57 UTCEPSS rescore
  41. 2026-07-15 02:00 UTCEPSS rescore
  42. 2026-07-13 22:30 UTCEPSS rescore
  43. 2026-07-13 14:08 UTCOSV refresh
  44. 2026-07-13 06:12 UTCEPSS rescore
  45. 2026-07-12 05:46 UTCEPSS rescore
  46. 2026-07-11 08:27 UTCEPSS rescore
  47. 2026-07-09 19:10 UTCEPSS rescore
  48. 2026-07-08 15:15 UTCEPSS rescore
  49. 2026-07-08 15:15 UTCEPSS rescore
  50. 2026-07-07 13:46 UTCEPSS rescore
  51. 2026-07-06 16:27 UTCEPSS rescore
  52. 2026-07-06 02:23 UTCEPSS rescore
  53. 2026-07-05 02:30 UTCEPSS rescore
  54. 2026-07-05 02:30 UTCEPSS rescore
  55. 2026-07-04 06:31 UTCEPSS rescore
  56. 2026-07-01 15:06 UTCEPSS rescore
  57. 2026-07-01 15:06 UTCEPSS rescore
  58. 2026-06-30 23:22 UTCEPSS rescore
  59. 2026-06-29 14:06 UTCEPSS rescore
  60. 2026-06-28 14:07 UTCEPSS rescore
  61. 2026-06-28 04:56 UTCEPSS rescore
  62. 2026-06-28 04:56 UTCEPSS rescore
  63. 2026-06-27 03:08 UTCEPSS rescore
  64. 2026-06-25 13:49 UTCEPSS rescore
  65. 2026-06-25 11:01 UTCOSV refresh
  66. 2026-06-24 14:05 UTCEPSS rescore
  67. 2026-06-23 21:32 UTCEPSS rescore
  68. 2026-06-22 14:25 UTCEPSS rescore
  69. 2026-06-22 14:25 UTCEPSS rescore
  70. 2026-06-21 14:56 UTCEPSS rescore
  71. 2026-06-21 14:56 UTCEPSS rescore
  72. 2026-06-21 01:59 UTCEPSS rescore
  73. 2026-06-21 01:59 UTCEPSS rescore
  74. 2026-06-19 19:25 UTCEPSS rescore
  75. 2026-06-18 17:52 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-0810?
CVE-2026-0810 is a high vulnerability published on January 26, 2026. A flaw was found in gix-date. The gixdate::parse::TimeBuf::asstr 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.…
When was CVE-2026-0810 disclosed?
CVE-2026-0810 was first published in the National Vulnerability Database on January 26, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-0810 actively exploited?
CVE-2026-0810 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 89.7% of all scored CVEs.
What is the CVSS score of CVE-2026-0810?
CVE-2026-0810 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-0810?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-0810, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-0810

Explore →

Is Your Infrastructure Affected by CVE-2026-0810?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs