Quick answers
- Is CVE-2024-8063 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2024-8063 being exploited in the wild.
- How severe is CVE-2024-8063?
- High severity, with a CVSS score of 7.5, published 20 March 2025.
- Which products and versions are affected?
- github.com/ollama/ollama (Go) <= 0.3.3, SEMVER:introduced=0, SEMVER:introduced=0,last_affected=0.3.3; Ollama <= 0.3.3; ollama (PyPI) ECOSYSTEM:introduced=0,last_affected=0.3.3.
- Is there a fix for CVE-2024-8063?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2024-8063 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2024-8063?
- Check whether you run github.com/ollama/ollama (Go), Ollama or ollama (PyPI) 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.
Technical details
A divide-by-zero vulnerability (CWE-369) exists in Ollama version 0.3.3 and earlier. The flaw is triggered during the import process of GGUF models when a Modelfile contains a crafted value for the 'block_count' parameter. When the server attempts to process this malformed model, it performs a division by zero, leading to an immediate application crash. This can be exploited by a remote attacker without authentication to cause a denial of service (DoS) condition. While the advisory lists version 0.3.3 as affected, later community reports suggest the issue may persist in subsequent versions.
Affected products
- Ollama Ollama <= 0.3.3
Identifiers
- CVE-2024-8063
- GHSA-2xf2-gjm6-g2c6
- GO-2025-3689
- PYSEC-2025-144
Timeline
- 2025-03-20: disclosed: NVD and GitHub Advisory published
- 2024-12-10: other: Issue reported on Ollama GitHub repository