Divide by Zero in ollama/ollama

published 2025-03-20 19 mo ago modified 2026-09-10 1 mo ago also GHSA-2xf2-gjm6-g2c6 , GO-2025-3689 , PYSEC-2025-144 , EUVD-2025-6935

cvss: 7.5; version 3.0, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.6%; EPSS 0.6% chance of exploitation in 30 days, percentile 51%
public exploits: 0; none known

A divide by zero vulnerability exists in ollama/ollama version v0.3.3. The vulnerability occurs when importing GGUF models with a crafted type for `block_count` in the Modelfile. This can lead to a denial of service (DoS) condition when the server processes the model, causing it to crash.

Patch / fix

distros 1

govulncheck-vulndb openSUSE Tumbleweed 0.0.20250515T200012-1.1

opensuse advisories openSUSE-SU-2025:15135-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2024-8063 updated 2026-03-02 cvss 7.5

ollama: Divide by Zero in ollama/ollama

Red Hat Ansible Automation Platform 2 ansible-automation-platform-24/lightspeed-rhel8, ansible-automation-platform-25/lightspeed-rhel8, ansible-automation-platform-26/lightspeed-rhel9, ansible-automation-platform-24/platform-resource-runner-rhel8, ansible-automation-platform-25/platform-resource-runner-rhel8, ansible-automation-platform-26/platform-resource-runner-rhel8
not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation: Proof of concept is public
Automatable: yes
Technical impact: partial
Assessed: 19 mo ago (2025-03-20)

Exploit prediction

0.64% chance of exploitation in the next 30 days, higher than 51% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

huntr.com https://huntr.com/bounties/fd8e1ed6-21d2-4c9e-8395-2098f11b7db9 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by	version	score	vector
CNA	3.0	7.5	CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVD	3.1	7.5	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
GitHub	3.0	7.5	CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected packages

ecosystem	package	affected	fixed in
go	github.com/ollama/ollama	<=0.3.3 all versions	no fix listed

Affected products

ollama ollama/ollama

Classification

Weakness

CWE-369 Divide By Zero

References

huntr.com /bounties/fd8e1ed6-21d2-4c9e-8395-2098f11b7db9
web, exploit, third-party-advisory, evidence
nvd.nist.gov /vuln/detail/CVE-2024-8063
advisory
github.com /ollama/ollama/issues/8020
web, report
github.com /ollama/ollama
package
github.com /pypa/advisory-database/tree/main/vulns/ollama/PYSEC-2025-144.yaml
web
github.com /advisories/GHSA-2xf2-gjm6-g2c6
advisory

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary