Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐹 Go

CVE-2025-0317

HIGH

CVE-2025-0317 is a high-severity (CVSS 7.5) CWE-369 vulnerability in github.com/ollama/ollama. O3 Security confirms whether CVE-2025-0317 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Divide By Zero in ollama/ollama

Also known asGHSA-9gcr-28rp-cc24GO-2025-3559
Published
Mar 20, 2025
Updated
Aug 7, 2026
Affected
1 pkg
Patched
None yet
Exploits
None indexed

Real-World Exposure

1 pkg affected
🐹github.com/ollama/ollama

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

A vulnerability in ollama/ollama versions <=0.3.14 allows a malicious user to upload and create a customized GGUF model file on the Ollama server. This can lead to a division by zero error in the ggufPadding function, causing the server to crash and resulting in a Denial of Service (DoS) attack.

Affected Packages

1 total
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/ollama/ollamaall versionsNo fix

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/ollama/ollama. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Remediation status

    No patched version of github.com/ollama/ollama has shipped for CVE-2025-0317 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

  3. Mitigate without a patch

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether CVE-2025-0317 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2025-0317. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

A vulnerability in ollama/ollama versions <=0.3.14 allows a malicious user to upload and create a customized GGUF model file on the Ollama server. This can lead to a division by zero error in the ggufPadding function, causing the server to crash and resulting in a Denial of Service (DoS) attack.
O3 Security · Impact-Aware SCA

Is CVE-2025-0317 in your dependencies?

O3 detects CVE-2025-0317 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.