CVE-2026-109351

6.5Medium

Published 12 Oct 2026 · NVD status: Awaiting Analysis · AI triage by gemini-3.8-flash

6.5Medium

Attack vector: Network
Complexity: Low
Privileges needed: None
User interaction: Required
Impact: High impact on availability
Weakness: CWE-770

Impact

Remote attackers can crash clone or fetch operations via an out-of-memory process abort. This requires an engineer or automated service to connect to a malicious remote Git repository.

Root cause

The pack-header parser directly allocates memory based on an unvalidated object count, allowing a 12-byte header with a spoofed 0xFFFFFFFF count to trigger an allocation of hundreds of gigabytes.

Affected systems

Gitoxide gix-pack before 0.75.0

CVSS v3.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

Fix & remediation

Upgrade the gix-pack dependency to version 0.75.0 or later. As an interim workaround, do not fetch from or clone untrusted remote repositories.

shell

$ cargo update -p gix-pack --precise 0.75.0

AI-suggested. Run it in staging first and check it against the vendor advisory. Why?

Ad · In-content banner

NVD description

Gitoxide gix-pack before 0.75.0 contains an uncontrolled memory allocation vulnerability that allows remote attackers to abort the process by supplying a huge pack-header object count. Malicious remotes can serve a 12-byte pack header claiming 0xFFFFFFFF objects, forcing Tree::with_capacity to reserve hundreds of gigabytes and crash clone or fetch operations.

References

Source: nvd.nist.gov/vuln/detail/CVE-2026-109351