CVE-2025-15514 — Ollama Multi-Modal Model Image Processing NULL Pointer Dereference
Ollama 0.11.5-rc0 through current version 0.13.5 contain a null pointer dereference vulnerability in the multi-modal model image processing functionality. When processing base64-encoded image data via the /api/chat endpoint, the application fails to validate that the decoded data represents valid media before passing it to the mtmd_helper_bitmap_init_from_buf function. This function can return NULL for malformed input, but the code does not check this return value before dereferencing the pointer in subsequent operations. A remote attacker can exploit this by sending specially crafted base64 image data that decodes to invalid media, causing a segmentation fault and crashing the runner process. This results in a denial of service condition where the model becomes unavailable to all users until the service is restarted.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.8% (30-day exploitation probability)+8
- Technical severity (high)+6
- CISA SSVC: exploitation "poc"+5
- Automatable exploitation (SSVC)+3
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Documented patch — huntr.com (NIST National Vulnerability Database)
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Ollama Ollama).
- The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
- Apply the fixed version or the patch documented under Remediation.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Ollama | Ollama | ≥ 0.11.6 and ≤ 0.13.5version 0.11.5version 0.11.5-rc0version 0.11.5-rc1version 0.11.5-rc2version 0.11.5-rc3version 0.11.5-rc4version 0.11.5-rc5 | Vulnerable | NIST National Vulnerability Database |
| Ollama | Ollama | ≥ v0.11.5-rc0 and ≤ 0.13.5 | Vulnerable | CVE Program (cve.org) e CISA ADP |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 8.7 | CVSS 4.0 | High | — | — | disclosure@vulncheck.com via NIST National Vulnerability Database |
| 8.7 | CVSS 4.0 | High | — | — | VulnCheck via CVE Program (cve.org) e CISA ADP |
| 7.5 | CVSS 3.1 | High | 3.9 | 3.6 | nvd@nist.gov via NIST National Vulnerability Database |
| 7.5 | CVSS 3.1 | High | 3.9 | 3.6 | 0b0ca135-0b70-47e7-9f44-1890c2a1c46c via NIST National Vulnerability Database |
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H (score shown at the top: nvd@nist.gov) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.77%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · ollama/ollama
- SSVC assessment updated
- Record published
- Fix documented
- CVSS changed · 7.5
- Source status changed · → Modified
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
6 on the record
- huntr.com/bounties/172df98b-07cd-41ea-a628-366f8cd525c0
- ollama.com/
- bugzilla.redhat.com/show_bug.cgi
- security.access.redhat.com/data/csaf/v2/vex/2025/cve-2025-15514.json
- www.vulncheck.com/advisories/ollama-multi-modal-image-processing-null-pointer-dereferen
- access.redhat.com/security/cve/CVE-2025-15514
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-103663 Path Traversal leading to Remote Code Execution in Ollama 7d
- High CVE-2026-65315 Ollama Remote Denial of Service via Attacker-Controlled Allocation in GGUF Metadata Parser Jul 21, 2026
- High CVE-2026-15685 Ollama downloadBlob Improper Validation of Array Index Denial-of-Service Vulnerability Jul 13, 2026
- High CVE-2026-5757 There exists an unauthenticated remote information disclosure vulnerability in Ollama's model quantization engine Jun 26, 2026
- Critical CVE-2026-7482 Ollama heap out-of-bounds read in GGUF tensor parsing leaks server process memory to unauthenticated remote attackers May 4, 2026
- Critical CVE-2026-42249 Remote Code Execution in Ollama via Update Mechanism Apr 29, 2026
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2025-15514 is "Ollama Multi-Modal Model Image Processing NULL Pointer Dereference", rated High. It affects Ollama (Ollama); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.5 describes technical severity. EPSS 0.77% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.