Security readout for executives and security teams
Plain-English summary
CVE-2026-0810 affects the Rust gix-date component. A date parsing buffer can produce invalid text that breaks internal safety assumptions, potentially causing crashes or incorrect behavior in software that uses it. Public data does not show active exploitation. Business urgency depends on whether your products or platforms include gix-date in reachable local processing paths.
Executive priority
Treat as a targeted high-priority dependency review, not an internet-wide emergency. Prioritize systems where gix-date is present and local users or workloads can influence date parsing. Monitor vendor advisories because current public evidence does not fully define affected versions or remediation details.
Technical view
The flaw is in gix_date::parse::TimeBuf::as_str, which may generate strings containing invalid non-UTF8 characters. Subsequent processing can trigger undefined behavior. The supplied CVSS is 7.1: local attack vector, low complexity, low privileges, no user interaction, with high integrity and availability impact and no confidentiality impact.
Likely exposure
Exposure is most likely in Rust applications or packaged products that depend on gix-date and process attacker-influenced date strings locally. Red Hat lists several OpenShift Logging packages with unknown status, while RHEL rust packages are listed as unaffected. The GitoxideLabs entry is marked default unaffected in the supplied data, so affected-version evidence is incomplete.
Exploitation context
The CVE is not listed as KEV, and the provided sources do not claim active exploitation. The CVSS indicates exploitation requires local access with low privileges and no user interaction. Practical impact appears to be application instability or unexpected integrity effects when malformed date strings reach vulnerable code paths.
Researcher notes
Key uncertainty is version scope. The description identifies the vulnerable function and undefined behavior mechanism, but the supplied affected list is mixed: Red Hat RHEL rust packages are unaffected, OpenShift Logging status is unknown, and GitoxideLabs is marked default unaffected. Avoid assuming exploitability without confirming dependency version and reachable parsing paths.
Mitigation direction
- Inventory applications and containers for the gix-date crate dependency.
- Review RustSec, GitoxideLabs, and Red Hat advisories for fixed versions or package guidance.
- Prioritize updates where gix-date processes untrusted or user-controlled date input.
- For Red Hat OpenShift Logging, track package status on the Red Hat CVE page.
- If no vendor fix is available, consider reducing exposure to untrusted date inputs.
Validation and detection
- Check SBOMs and dependency manifests for gix-date usage.
- Confirm whether vulnerable code paths call TimeBuf::as_str on parsed date data.
- Review vendor advisories for exact affected and fixed versions.
- Verify Red Hat package status before declaring OpenShift Logging exposure.
- Document whether local low-privilege users can influence processed date strings.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-135: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-0810 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H1.85.2Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.1HighVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://access.redhat.com/security/cve/CVE-2026-0810CVE reference · vdb-entry, x_refsource_REDHAT
- RHBZ#2427057CVE reference · issue-tracking, x_refsource_REDHAT
- https://crates.io/crates/gix-dateCVE reference
- https://github.com/GitoxideLabs/gitoxide/issues/2305CVE reference
- https://rustsec.org/advisories/RUSTSEC-2025-0140.htmlCVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Incorrect Calculation of Multi-Byte String Length
Incorrect Calculation of Multi-Byte String Length represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.