Quick answers
- Is CVE-2026-109349 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-109349 being exploited in the wild.
- How severe is CVE-2026-109349?
- Medium severity, with a CVSS score of 6.5, published 12 October 2026.
- Which products and versions are affected?
- GitoxideLabs Gix-Pack before 0.75.0.
- Is there a fix for CVE-2026-109349?
- Yes: fixed in 0.75.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-109349 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-109349?
- Check whether you run GitoxideLabs Gix-Pack at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 0.75.0
Technical details
The pack header decoder in gix-pack/src/data/header.rs explicitly accepts version 3 (returning Ok(Version::V3)), but immediately after, BytesToEntriesIter::new_from_header uses assert_eq!(version, Version::V2) to verify the version—a hard assertion that is compiled into release builds. An attacker can send a pack stream beginning with bytes 50 41 43 4B 00 00 00 03 (PACK version 3) to trigger the panic; with panic="unwind" and no catch_unwind in the read path, this unwinds to the process abort. The fix treats non-V2 versions as a graceful error instead of a panic.
Affected products
- GitoxideLabs gix-pack before 0.75.0
Timeline
- 2026-09-25: disclosed
- 2026-10-12: advisory