CVE-2026-7482

CRITICALNVD 9.19.1—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.1 under NVD CVSS v3. EPSS exploit probability: 1.9%, top 22% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
9.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 2%CVSS: 9.1Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Ollama before 0.17.1 contains a heap out-of-bounds read vulnerability in the GGUF model loader. The /api/create endpoint accepts an attacker-supplied GGUF file in which the declared tensor offset and size exceed the file's actual length; during quantization in fs/ggml/gguf.go and server/quantization.go (WriteTo()), the server reads past the allocated heap buffer. The leaked memory contents may include environment variables, API keys, system prompts, and concurrent users' conversation data, and can be exfiltrated by uploading the resulting model artifact through the /api/push endpoint to an attacker-controlled registry. The /api/create and /api/push endpoints have no authentication in the upstream distribution. Default deployments bind to 127.0.0.1, but the documented OLLAMA_HOST=0.0.0.0 configuration is widely used in practice (large public-internet exposure observed).

CVSS v3
9.1
EG Score
9.1(medium)
EG Risk
72(Track)
EG Risk 72/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity91% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
2%
EPSS %ILE
82%
KEV
Not listed

Published

May 4, 2026

Last Modified

May 11, 2026

Advisory Details (3)

Auto-updated Aug 1, 2026
Patch available. Sources: github_commit, github_pr, github_release.
github_release Patch Available

v0.17.1

Patch available: ollama/ollama v0.17.1

https://github.com/ollama/ollama/releases/tag/v0.17.1
github_pr

ggml: ensure tensor size is valid

Fix merged in ollama/ollama PR #14406 on 2026-02-25 — awaiting tagged release

https://github.com/ollama/ollama/pull/14406
github_commit

commit 88d57d0483cc (ollama/ollama)

Fix landed in ollama/ollama commit 88d57d0483cc — awaiting tagged release

https://github.com/ollama/ollama/commit/88d57d0483cca907e0b23a968c83627a20b21047

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/ollama/ollama—0.17.1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 6× in last 7d / 31× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 150 total refreshes for this CVE.

  1. 2026-09-15 03:12 UTCEPSS rescore
  2. 2026-09-15 03:12 UTCEPSS rescore
  3. 2026-09-11 18:10 UTCOSV refresh
  4. 2026-09-11 14:53 UTCEPSS rescore
  5. 2026-09-11 14:53 UTCEPSS rescore
  6. 2026-09-08 22:01 UTCEPSS rescore
  7. 2026-09-06 13:48 UTCEPSS rescore
  8. 2026-09-04 05:07 UTCEPSS rescore
  9. 2026-09-02 14:12 UTCEPSS rescore
  10. 2026-09-01 13:54 UTCEPSS rescore
  11. 2026-09-01 04:40 UTCEPSS rescore
  12. 2026-09-01 04:40 UTCEPSS rescore
  13. 2026-08-30 19:18 UTCEPSS rescore
  14. 2026-08-30 19:17 UTCEPSS rescore
  15. 2026-08-30 01:22 UTCEPSS rescore
  16. 2026-08-28 21:42 UTCEPSS rescore
  17. 2026-08-27 14:25 UTCEPSS rescore
  18. 2026-08-26 14:47 UTCEPSS rescore
  19. 2026-08-25 13:49 UTCEPSS rescore
  20. 2026-08-24 14:18 UTCEPSS rescore
  21. 2026-08-23 21:36 UTCEG score recompute
  22. 2026-08-23 00:19 UTCEPSS rescore
  23. 2026-08-21 23:49 UTCEPSS rescore
  24. 2026-08-20 22:56 UTCEPSS rescore
  25. 2026-08-19 17:04 UTCEPSS rescore
Show 75 more
  1. 2026-08-18 13:49 UTCEPSS rescore
  2. 2026-08-18 13:49 UTCEPSS rescore
  3. 2026-08-17 13:47 UTCEPSS rescore
  4. 2026-08-17 13:13 UTCEG score recompute
  5. 2026-08-16 14:56 UTCEPSS rescore
  6. 2026-08-16 14:56 UTCEPSS rescore
  7. 2026-08-16 05:04 UTCEG score recompute
  8. 2026-08-16 02:15 UTCEPSS rescore
  9. 2026-08-15 01:31 UTCEPSS rescore
  10. 2026-08-14 03:39 UTCEG score recompute
  11. 2026-08-13 22:00 UTCEPSS rescore
  12. 2026-08-12 17:19 UTCEG score recompute
  13. 2026-08-12 13:51 UTCEPSS rescore
  14. 2026-08-11 16:11 UTCEG score recompute
  15. 2026-08-11 13:43 UTCEPSS rescore
  16. 2026-08-11 01:41 UTCEG score recompute
  17. 2026-08-11 00:00 UTCEPSS rescore
  18. 2026-08-09 16:51 UTCEG score recompute
  19. 2026-08-09 13:47 UTCEPSS rescore
  20. 2026-08-09 02:46 UTCEG score recompute
  21. 2026-08-08 16:37 UTCEPSS rescore
  22. 2026-08-07 20:08 UTCEG score recompute
  23. 2026-08-06 17:01 UTCEG score recompute
  24. 2026-08-06 13:47 UTCEPSS rescore
  25. 2026-08-05 22:30 UTCEG score recompute
  26. 2026-08-05 19:17 UTCEPSS rescore
  27. 2026-08-05 19:17 UTCEPSS rescore
  28. 2026-08-04 15:10 UTCEPSS rescore
  29. 2026-08-04 10:39 UTCEPSS rescore
  30. 2026-08-03 20:10 UTCEG score recompute
  31. 2026-08-03 10:36 UTCEPSS rescore
  32. 2026-08-02 05:30 UTCEG score recompute
  33. 2026-08-02 02:27 UTCEPSS rescore
  34. 2026-08-01 04:16 UTCEPSS rescore
  35. 2026-07-30 16:28 UTCEPSS rescore
  36. 2026-07-30 01:30 UTCEPSS rescore
  37. 2026-07-28 15:37 UTCEPSS rescore
  38. 2026-07-27 14:14 UTCEPSS rescore
  39. 2026-07-26 14:54 UTCEPSS rescore
  40. 2026-07-25 14:18 UTCEPSS rescore
  41. 2026-07-24 14:18 UTCEPSS rescore
  42. 2026-07-23 14:18 UTCEPSS rescore
  43. 2026-07-23 14:18 UTCEPSS rescore
  44. 2026-07-23 03:22 UTCEG score recompute
  45. 2026-07-22 14:08 UTCEPSS rescore
  46. 2026-07-22 14:08 UTCEPSS rescore
  47. 2026-07-21 15:25 UTCEPSS rescore
  48. 2026-07-21 15:25 UTCEPSS rescore
  49. 2026-07-20 22:02 UTCOSV refresh
  50. 2026-07-20 17:08 UTCEPSS rescore
  51. 2026-07-19 14:31 UTCEPSS rescore
  52. 2026-07-19 02:29 UTCEPSS rescore
  53. 2026-07-18 10:04 UTCEPSS rescore
  54. 2026-07-16 17:03 UTCEPSS rescore
  55. 2026-07-15 16:57 UTCEPSS rescore
  56. 2026-07-15 02:00 UTCEPSS rescore
  57. 2026-07-13 22:31 UTCEPSS rescore
  58. 2026-07-13 06:13 UTCEPSS rescore
  59. 2026-07-12 05:46 UTCEPSS rescore
  60. 2026-07-11 08:27 UTCEPSS rescore
  61. 2026-07-11 08:27 UTCEPSS rescore
  62. 2026-07-09 19:10 UTCEPSS rescore
  63. 2026-07-09 19:10 UTCEPSS rescore
  64. 2026-07-08 15:16 UTCEPSS rescore
  65. 2026-07-08 15:16 UTCEPSS rescore
  66. 2026-07-07 13:46 UTCEPSS rescore
  67. 2026-07-07 13:46 UTCEPSS rescore
  68. 2026-07-06 16:27 UTCEPSS rescore
  69. 2026-07-06 16:27 UTCEPSS rescore
  70. 2026-07-06 02:23 UTCEPSS rescore
  71. 2026-07-06 02:23 UTCEPSS rescore
  72. 2026-07-05 02:31 UTCEPSS rescore
  73. 2026-07-05 02:30 UTCEPSS rescore
  74. 2026-07-04 06:31 UTCEPSS rescore
  75. 2026-07-04 06:31 UTCEPSS rescore

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoC0x0OZ/CVE-2026-7482-PoC
    First seen May 5, 2026

    1day vuln research I guess

    Open source ↗

Frequently asked(5)

What is CVE-2026-7482?
CVE-2026-7482 is a critical vulnerability published on May 4, 2026. Ollama before 0.17.1 contains a heap out-of-bounds read vulnerability in the GGUF model loader. The /api/create endpoint accepts an attacker-supplied GGUF file in which the declared tensor offset and size exceed the file's actual length; during quantization in fs/ggml/gguf.go and…
When was CVE-2026-7482 disclosed?
CVE-2026-7482 was first published in the National Vulnerability Database on May 4, 2026, with the most recent update on May 11, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-7482 actively exploited?
CVE-2026-7482 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2% probability of exploitation in the next 30 days, which ranks it in the top 18.1% of all scored CVEs.
What is the CVSS score of CVE-2026-7482?
CVE-2026-7482 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2026-7482?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-7482, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-7482

Explore →

Is Your Infrastructure Affected by CVE-2026-7482?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs