Cyber Resilience

CVE-2024-12055

Memory Safety in Ollama ≤ 0.3.14

Public PoCMemory Safety
Published
20 March 2025
Modified
13 May 2025
CVSS Score v3.1 7.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS Score 0.0082 54th percentile
Risk Priority 59 floored blend · peak EPSS

Summary

CVE-2024-12055 is a high-severity Out-of-bounds Read (CWE-125) vulnerability in Ollama Ollama. Its CVSS base score is 7.5 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 46% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

This vulnerability is AI-related — categorised as NLP and Transformers; in the Data-Related Vulnerabilities risk domain.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-8 (Security and Privacy Engineering Principles) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2024-12055 is a vulnerability in Ollama versions up to and including 0.3.14, stemming from an out-of-bounds read in the gguf.go file and classified under CWE-125. This flaw allows a malicious user to create a customized GGUF model file that can be uploaded to a public Ollama server. When the server processes the malicious model, it crashes, resulting in a Denial of Service (DoS) condition. The issue carries a CVSS v3.1 base score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H), highlighting its high availability impact.

Any unauthenticated attacker with network access can exploit this vulnerability due to its lack of prerequisite privileges or user interaction. By crafting and uploading the malicious GGUF model file to the public Ollama server, the attacker triggers the out-of-bounds read during model processing, causing the server to crash and disrupting service availability for all users.

For mitigation details, security practitioners should consult the advisory referenced at https://huntr.com/bounties/7b111d55-8215-4727-8807-c5ed4cf1bfbe, which documents the issue discovered through a bug bounty program. Upgrading to Ollama versions beyond 0.3.14 is implied as a resolution based on the affected version scope.

EU & UK References

Vulnerability Data

A vulnerability in Ollama versions <=0.3.14 allows a malicious user to create a customized gguf model file that can be uploaded to the public Ollama server. When the server processes this malicious model, it crashes, leading to a Denial of…

more

Service (DoS) attack. The root cause of the issue is an out-of-bounds read in the gguf.go file.

CWE(s)
CWE-125

AI Security AnalysisAI

AI Category
NLP and Transformers
Risk Domain
Data-Related Vulnerabilities
OWASP Top 10 for LLMs 2025
None mapped
Classification Reason
Matched keywords: ollama

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
attack.mitre.org →
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
attack.mitre.org →
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
attack.mitre.org →
T1211 Exploitation for Stealth Stealth
Adversaries may exploit vulnerabilities to evade detection by hiding activity, suppressing logging, or operating within trusted or unmonitored components.
attack.mitre.org →
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-7482Same product: Ollama Ollama
CVE-2026-5757Same product: Ollama Ollama
CVE-2024-39720Same product: Ollama Ollama
CVE-2025-1975Same product: Ollama Ollama
CVE-2026-15685Same product: Ollama Ollama
CVE-2025-66959Same product: Ollama Ollama
CVE-2025-66960Same product: Ollama Ollama
CVE-2025-44779Same product: Ollama Ollama
CVE-2026-7020Same product: Ollama Ollama
CVE-2025-51471Same product: Ollama Ollama

Affected Assets

ollama
ollama
≤ 0.3.14

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation directly finds out-of-bounds read flaws through static analysis, fuzzing, and dynamic bounds checks.

SA-8 Security and Privacy Engineering Principles partial match

Secure engineering principles require bounds checking and memory-safe constructs that stop out-of-bounds reads from being introduced.

SC-39 Process Isolation partial match

Process isolation confines the effects of an out-of-bounds read to the compromised process.

SI-10 Information Input Validation partial match

Input validation rejects malformed indices or lengths that would otherwise cause reads outside buffer bounds.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure-development practices such as bounds checking and memory-safe languages directly prevent out-of-bounds reads.

ID.RA-01 partial match
prevents

Vulnerability scanning and recording can discover instances of out-of-bounds reads after code is deployed.

PR.PS-02 partial match
prevents

Routine patching replaces vulnerable code containing out-of-bounds read flaws.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing in development and acceptance includes fuzzing and static analysis that detect out-of-bounds read defects before release.

A.8.15 Logging partial match
finds

Logging can record evidence of an out-of-bounds read but does not prevent the weakness itself.

A.8.25 Secure development life cycle partial match
prevents

Secure development life cycle mandates input validation and bounds checking that directly prevent out-of-bounds reads.

A.8.26 Application security requirements partial match
prevents

Application security requirements include explicit bounds and memory-safety specifications that mitigate buffer over-reads.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure system architecture and engineering principles require memory-safe design patterns and runtime protections against out-of-bounds access.

A.8.28 Secure coding partial match
prevents

Secure coding standards explicitly forbid unsafe pointer arithmetic and mandate bounds-checked reads, eliminating CWE-125.

References