CVE-2025-63389
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 · uneditedA critical authentication bypass vulnerability exists in Ollama platform's API endpoints in versions prior to and including v0.12.3. The platform exposes multiple API endpoints without requiring authentication, enabling remote attackers to perform unauthorized model management operations.
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 · high confidenceOllama platform versions up to and including v0.12.3 expose API endpoints without authentication, allowing remote attackers to bypass authentication controls and perform unauthorized model management operations such as model deletion, modification, or injection.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 0.12.3CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Determine installed Ollama versionRun 'ollama --version' or check the binary metadata to identify the exact version number installed in your environmentAffected if The installed version is 0.12.3 or any lower version (e.g., 0.12.2, 0.12.1, 0.11.x, etc.)
-
Verify API network binding configurationCheck if Ollama is bound to a network interface accessible from remote hosts by examining the server configuration or running 'netstat'/'ss' commands on the Ollama port (typically 11434) to see binding addressAffected if Ollama API is listening on 0.0.0.0 or a publicly accessible IP rather than localhost/127.0.0.1
-
Test API authentication requirementAttempt an unauthenticated API request to the Ollama endpoints (such as /api/models or /api/delete) using curl or similar tool without providing any credentials or authorization headersAffected if The API returns successful responses without requiring any authentication tokens, headers, or credentials
-
Review Ollama configuration for authentication settingsExamine the Ollama configuration file or environment variables for any authentication, authorization, or access control settings that may be definedAffected if No authentication mechanism is configured or enabled in the Ollama configuration
Your environment is affected if Ollama version 0.12.3 or lower is installed AND the API is network-accessible without requiring authentication credentials.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataImplement authentication and authorization checks on all API endpoints, enforce proper session/token validation, and upgrade to a version beyond v0.12.3 that addresses this authentication bypass.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-63389 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-63389 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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