← Back
CVE-2025-1975
Vulnerability in github.com/ollama/ollama (CVE-2025-1975)
Summary
vulnerability in github.com/ollama/ollama (CVE-2025-1975). Risk of unauthorized operations or information disclosure.
AI summary snake-internal / snake-template-v1
A weakness called CVE-2025-1975 was discovered in Ollama Server Vulnerable to.
Severity is Info. Low severity or not yet rated.
What you should do: update the affected software to the latest version. If unsure, ask your IT team or search the vendor's site for "Ollama Server Vulnerable to CVE-2025-1975".
CVE-2025-1975 (Ollama Server Vulnerable to). Severity: Info. Category: CWE-129.
Response plan:
1. Check the vendor advisory for affected versions and the patched release.
2. If a vulnerable version is running in production, schedule maintenance (urgency from KEV/CVSS).
3. If no patch yet, mitigate via WAF rule, disabling the affected feature, etc.
4. Monitor logs / SIEM for known IOC and PoC signatures of this CVE.
PoCs and fix commits: see the 'References' section, MITRE, and NVD.
❓ What is the problem
A weakness (CVE-2025-1975) in Ollama Server Vulnerable to. A serious software flaw has been identified.
📍 Affected scope
Target versions of Ollama Server Vulnerable to (see vendor advisory). If running in production, identify exposure immediately.
🔥 Severity
Severity: Info. Low severity or not yet rated.
🔧 How to fix
Update to the patched release as listed in the vendor advisory. (Typical mitigation pattern for CWE-129)
🛡️ Workaround
If a patch is not yet available, consider disabling the affected feature, applying WAF rules, blocking via network ACLs, or isolating the vulnerable version.
🔍 Detection
Check version information, scan dependencies via SBOM, and monitor SIEM for IOC and PoC signatures related to this CVE.
Response Actions (7 steps)
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 し、稼働しているサービス・バージョンを把握する。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
Go
github.com/ollama/ollama
[{"type":"SEMVER","events":[{"introduced":"0"}]}]
PyPI
ollama
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"last_affected":"0.5.11"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2025-1975
- advisory https://github.com/advisories/GHSA-wrh5-cmwx-q2qr
- package https://github.com/ollama/ollama
- web https://huntr.com/bounties/921ba5d4-f1d0-4c66-9764-4f72dffe7acd
- web https://pkg.go.dev/vuln/GO-2025-3695
- web https://github.com/pypa/advisory-database/tree/main/vulns/ollama/PYSEC-2025-145.yaml