CVE-2026-7482: Ollama out-of-bounds read (CVSS 9.1)

Description

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 3.1 breakdown

Attack vectorNetwork

Attack complexityLow

Privileges requiredNone

User interactionNone

ScopeUnchanged

ConfidentialityHigh

IntegrityNone

AvailabilityHigh

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H

Affected products

Ollama< 0.17.1

Remediation

Fixed in

Ollama≥ 0.17.1

Patch & vendor advisories

References

https://github.com/ollama/ollama/commit/88d57d0483cca907e0b23a968c83627a20b21047Patch
https://github.com/ollama/ollama/pull/14406Issue TrackingPatch
https://github.com/ollama/ollama/releases/tag/v0.17.1Release Notes

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

Frequently asked

Is CVE-2026-7482 being actively exploited?

CVE-2026-7482 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.71%.

How severe is CVE-2026-7482?

CVE-2026-7482 has a CVSS 3.1 base score of 9.1, rated critical. EPSS estimates a 0.71% probability of exploitation.

Which products are affected by CVE-2026-7482?

Affected products include Ollama.

How do I fix CVE-2026-7482?

Upgrade affected software to a fixed version, for example Ollama 0.17.1 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-7482 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation works Book a demo