CVE-2024-39720

Exp

An issue was discovered in Ollama before 0.1.46. An attacker can use two HTTP requests to upload a malformed GGUF file containing just 4 bytes starting with the GGUF custom magic header. By leveraging a custom Modelfile that includes a FROM statement pointing to the attacker-controlled blob file, the attacker can crash the application through the CreateModel route, leading to a segmentation fault (signal SIGSEGV: segmentation violation).

Published: 2024-10-31 Last update: 2025-05-13 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2024-39720 is rated High Exploit Risk (64.7/100): CVSS High severity, with low exploitation likelihood (EPSS 0.25%). 1 public exploit reference(s) are indexed (Exploit-DB). Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2024-39720

EDB-ID Source Kind Published Link
— nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2024-39720

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-03-08 0.17% 0.25% +0.08%
2 2026-02-20 0.25% 0.17% -0.08%
3 2026-01-26 — 0.25% —

Full EPSS history (13 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2024-39720

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
8.2 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 4.2 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2024-39720

GitHub Security Advisory for CVE-2024-39720

OS Trackers for CVE-2024-39720

vendor priority summary link
suse high CVE-2024-39720 severity important: SUSE including 7 source package names (cloud-netconfig-azure-1.15-slfo.1.1_1.1, cloud-netconfig-ec2-1.15-slfo.1.1_1.1, …), 34 product×package rows across 26 product lines (Container suse/sl-micro/6.0/baremetal-os-container, Container suse/sl-micro/6.0/toolbox, … (26 product lines)): Fixed 34. https://www.suse.com/security/cve/CVE-2024-39720/

Affected software / configurations for CVE-2024-39720

Vendor Product Version Raw CPE
ollama ollama < 0.1.46 cpe:2.3:a:ollama:ollama:*:*:*:*:*:*:*:*

References for CVE-2024-39720

cvelogic Threat Intelligence