Out-of-Bounds Read in github.com/ollama/ollama (CVE-2026-7482)
Summary
Vulnerability in github.com/ollama/ollama (CVE-2026-7482). Confidential information can be exposed externally. Mitigation: upgrade to 0.17.1 or later.
Original description
The description as published by the source.
Ollama is vulnerable to a heap out-of-bounds read in its GGUF model loader. A specially crafted GGUF file can cause the loader to read beyond the allocated heap buffer, potentially leading to a denial of service (crash).
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-7482 has been found in github.com/ollama/ollama.
Confidential information can be exposed externally. CVSS score: 9.1/10.
What to do: upgrade github.com/ollama/ollama to 0.17.1 or later.
If unsure, ask your IT team or search "github.com/ollama/ollama CVE-2026-7482" on the vendor's site.
CVE-2026-7482 (github.com/ollama/ollama) — CWE-125 / CVSS v3 9.1
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 0.17.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Out-of-bounds read (CWE-125) exists in github.com/ollama/ollama.
Check the vendor advisory for the affected versions of github.com/ollama/ollama.
Severity: Critical (CVSS 9.1/10). Confidential information can be exposed externally.
Update to 0.17.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/ollama/ollama' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/ollama/ollama' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/ollama/ollamaを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/ollama/ollama to 0.17.1ステージング環境で 0.17.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- patch github.com
- web github.com