dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2026-5530

MEDIUM · 6.3 CVSS v3.1 Published 2026-04-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A flaw has been found in Ollama up to 0.18.1. This issue affects some unknown processing of the file server/download.go of the component Model Pull API. Executing a manipulation can lead to server-side request forgery. The attack can be launched remotely. The vendor was contacted early about this disclosure but did not respond in any way.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Server-side request forgery (SSRF) vulnerability in Ollama's Model Pull API file server component (download.go). Remote attackers can manipulate the API to cause the server to make arbitrary requests to internal or external resources, potentially accessing internal services or exfiltrating data.

MitigationImplement strict URL allowlist validation and input sanitization for the Model Pull API; restrict outbound network access via firewall rules; monitor for anomalous outbound connections until an official patch is released.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Ollama installation and version
    Run 'ollama --version' to retrieve the installed version number, or check the binary path (typically /usr/local/bin/ollama or /usr/bin/ollama) for its version metadata
    Affected if The version is 0.18.1 or any earlier version (the vulnerability affects versions up to and including 0.18.1)
  2. Verify Model Pull API is accessible
    Check if the Ollama service is running and its API endpoints are exposed. Look for the default port (11434) listening with 'netstat -tlnp | grep 11434' or 'ss -tlnp | grep 11434'. The API typically responds at http://localhost:11434/api/pull
    Affected if The Ollama API port (default 11434) is open and reachable, enabling the Model Pull API endpoint
  3. Confirm network egress configuration
    Review firewall rules, iptables, or cloud security groups to determine if the Ollama server can make outbound HTTP/HTTPS requests to arbitrary destinations. Check for unrestricted egress rules or lack of egress filtering
    Affected if The server has unrestricted outbound network access, allowing it to reach internal services or attacker-controlled URLs
  4. Check for URL allowlisting controls
    Inspect Ollama configuration files (typically in /etc/ollama, ~/.ollama, or environment variables) for any URL domain restrictions or allowlist settings related to model downloads
    Affected if No URL allowlisting or domain restrictions are configured for the Model Pull API, meaning arbitrary URLs can be specified during model pulls

You are affected if Ollama version 0.18.1 or earlier is installed, the Model Pull API is accessible, and no URL allowlisting or network restrictions are in place to prevent arbitrary request targets.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict URL allowlist validation and input sanitization for the Model Pull API; restrict outbound network access via firewall rules; monitor for anomalous outbound connections until an official patch is released.

Recommended fix Moderate confidence

Ollama 0.18.2 or later (upgrade to the latest available version)

  1. Check your current Ollama version by running: ollama --version
  2. Stop the Ollama service if running: systemctl stop ollama (or appropriate command for your setup)
  3. Update Ollama to the latest version using your installation method: brew upgrade ollama (macOS), or check the official installation guide for other methods
  4. Verify the upgrade was successful by running: ollama --version
  5. Restart the Ollama service: systemctl start ollama
Caveat Minor version upgrade; unlikely to have breaking changes, but review release notes for any configuration changes

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-5530 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-5530 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data