CVE-2026-109348
Received Received - Intake

Gitoxide gix-mailmap CPU Exhaustion via Quadratic Parsing

Publication date: 2026-10-12

Last updated on: 2026-10-12

Assigner: VulnCheck

Description
Gitoxide gix-mailmap before 0.35.0 contains a denial of service vulnerability that allows attackers to exhaust CPU through quadratic-time parsing in Snapshot::from_bytes. Attackers can commit a crafted .mailmap with descending-ordered entries forcing repeated front inserts, blocking workers running log, blame, or shortlog for minutes.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-12
Last Modified
2026-10-12
Generated
2026-10-12
AI Q&A
2026-10-12
EPSS Evaluated
N/A
NVD
CVE-2026-109348
EUVD
EUVD-2026-97650

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
GitoxideLabs gix-mailmap 0

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-407 An algorithm in a product has an inefficient worst-case computational complexity that may be detrimental to system performance and can be triggered by an attacker, typically using crafted manipulations that ensure that the worst case is being reached.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability is a denial of service issue in Gitoxide's gix-mailmap before version 0.35.0. It involves quadratic-time parsing in the Snapshot::from_bytes function when processing .mailmap files. Attackers can exploit this by creating a crafted .mailmap file with entries in descending order, forcing repeated front inserts during parsing. This causes CPU exhaustion, blocking operations like log, blame, or shortlog for minutes.

Detection Guidance

Check if your system uses gix-mailmap versions before 0.35.0 by running: gitoxide --version or cargo list --manifest-path /path/to/project/Cargo.toml. Monitor CPU usage spikes during .mailmap file processing. Look for unusually slow git operations like log, blame, or shortlog on repositories with large .mailmap files.

Impact Analysis

If you use Gitoxide's gix-mailmap in versions before 0.35.0, an attacker could commit a malicious .mailmap file to a repository you clone or interact with. This would cause your CPU to spike and potentially freeze for minutes while processing the file, disrupting your workflow. Services processing untrusted repositories are particularly at risk.

Compliance Impact

This vulnerability primarily causes CPU exhaustion through denial-of-service attacks, which may indirectly impact compliance by disrupting system availability and performance. However, the CVE does not directly link to specific compliance violations for standards like GDPR or HIPAA, as those depend on data processing context rather than technical flaws alone.

Mitigation Strategies

Upgrade gix-mailmap to version 0.35.0 or later using: cargo update -p gix-mailmap. Avoid processing untrusted repositories with large .mailmap files. Implement size limits for .mailmap files in your git hooks or CI/CD pipelines. Monitor for suspicious repository commits containing descending-ordered .mailmap entries.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-109348. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart