Skip to main content

ChatOllama CVE-2026-111702

| EUVDEUVD-2026-102994 HIGH
Authorization Bypass Through User-Controlled Key (CWE-639)
2026-10-16 VulnCheck GHSA-7pf8-cp62-gc3p
8.7
CVSS 4.0 · Vendor: VulnCheck
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Reach ChatOllama API endpoint
  2. Exploit
    Enumerate sequential knowledgebase IDs
  3. Execution
    Request GET /api/knowledgebases/{id}
  4. Impact
    Exfiltrate other users' private documents

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Object-level authorization, IDOR prevention
Exploitation Conditions

Exploitation requires network reachability to a ChatOllama instance (through commit 96c3ce5) and that knowledge bases are referenced by predictable sequential integer IDs, which the application does not authorize against the requesting user. The attacker supplies arbitrary IDs to GET /api/knowledgebases/{id} or to the knowledgebaseId parameter of POST /api/models/chat. The supplied CVSS vector states PR:N (no privileges) and UI:N (no interaction); the main limiting factor is whether a given deployment places the API behind network restrictions or a login requirement - defenders should confirm whether their instance enforces authentication, since a typical IDOR presumes at least a valid user session even though the vector asserts none. Impact is read-only disclosure of other users' knowledge-base metadata and retrieved document content; no write or availability impact.

Impact

The input provides only a CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N/VC:H with no integrity or availability impact, base score 8.7, 'High'), reflecting a network-reachable, low-complexity, no-interaction read-only IDOR (CWE-639). No EPSS score is provided, so exploitation probability cannot be quantified. Not listed in CISA KEV and no POC flag is set, so exploitation status is 'no public exploit identified at time of analysis' - however, a detailed third-party technical writeup (hackmd.io) documents the exact vulnerable endpoints and the sequential-id enumeration method, meaning the barrier to building a working exploit is effectively trivial despite no packaged POC. No SSVC decision data is supplied. On balance this is a genuine confidentiality risk (trivial, automatable enumeration of sequential IDs leaking other users' private knowledge-base metadata and retrieved document content) but is tempered by the product's small real-world footprint: it affects a niche self-hosted open-source project, not widely deployed enterprise software. The high CVSS reflects ease-of-exploit and data sensitivity, not breadth of exposure. One caveat: CWE-639 IDOR normally presumes an authenticated foothold, yet the supplied vector states PR:N; verify whether the targeted ChatOllama instance enforces login, as this materially changes who can exploit it.

Exploit ScenarioDerived

A remote attacker reachable to a ChatOllama instance iterates sequential integer knowledge-base IDs against GET /api/knowledgebases/{id} (or via the knowledgebaseId parameter of POST /api/models/chat) and harvests metadata and retrieved document content belonging to other users' private knowledge bases. Because the attack is low-complexity and requires no user interaction, it is easily scriptable to enumerate every knowledge base on the server. No packaged exploit is published, but a public technical writeup details the exact vulnerable endpoints and method.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.4% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 16, 2026

An insecure direct object reference (IDOR) in ChatOllama (sugarforever/chat-ollama) through commit 96c3ce5 lets remote attackers read other users' private knowledge bases by supplying sequential integer identifiers. According to the supplied CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N, VC:H with no integrity or availability impact, base 8.7), the exposure is a network-reachable, low-complexity, read-only disclosure that requires no privileges or user interaction, although defenders should confirm whether their deployment actually enforces authentication in front of the API. Affected endpoints are GET /api/knowledgebases/{id} and the knowledgebaseId parameter of POST /api/models/chat; the impact is limited to metadata and retrieved document content of other tenants, with no write or denial-of-service component. No public exploit code or confirmed active exploitation was identified at time of analysis; the primary risk driver is the predictable, non-tenant-scoped ID space rather than a remotely weaponized exploit.

RemediationAI

No vendor-released patch was identified at time of analysis; the code references point to the vulnerable handlers at commit 6f4245a96b58ce8833a8c51d90d923b0e9814784 rather than to a fixed release, so treat any remediation as a code-level or deployment-level change. The correct code fix, consistent with the referenced file paths, is to enforce per-object authorization in both server/api/knowledgebases/[id].get.ts and the knowledgebaseId branch of server/api/models/chat/index.post.ts - resolve the knowledge base only when it belongs to the authenticated principal (or an explicitly shared scope) - and to replace sequential integer IDs with unguessable UUIDs or ULIDs and return 404 rather than 403 on unauthorized lookups so the ID space cannot be enumerated; note that switching to UUIDs requires a data migration and breaks any external integrations that cached integer IDs. Until that fix is deployed, compensating controls are: require authentication in front of the entire /api surface (reverse proxy with an auth layer or the app's own login), and network-restrict the instance to trusted clients (VPN, mTLS, firewall allow-listing), accepting that this removes the public-facing convenience of the chat UI and does not stop an authenticated low-privileged tenant from enumerating peers' IDs. Additionally, if auditability matters, enable request logging for GET /api/knowledgebases/{id} and POST /api/models/chat to detect sequential ID scanning, understanding that logging is detective only and not a preventive control. Track https://github.com/sugarforever/chat-ollama and the VulnCheck advisory above for an upstream fix commit, and re-validate after any pull of newer commits since the CPE wildcard does not indicate a known fixed version.

Affected VersionsENISA

chat-ollama 0 ≤96c3ce50c3ba4ec3b19f126f50c035f84183f9fc

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The flaw is CWE-639 (Authorization Bypass Through User-Controlled Key), the classic IDOR pattern, and it sits in Nuxt/Nitro server API handlers of the ChatOllama project (CPE cpe:2.3:a:sugarforever:chat-ollama:*:*:*:*:*:*:*:*). Two request paths accept a caller-controlled knowledgebase identifier: the GET handler at server/api/knowledgebases/[id].get.ts (lines 25-34) and the POST handler at server/api/models/chat/index.post.ts (lines 392-427), which resolves a knowledge base from the knowledgebaseId parameter before performing retrieval-augmented chat. Because the handlers look up the object by primary key without verifying that the key belongs to the requesting principal, and because those keys are sequential integers rather than unguessable identifiers, an attacker can walk the ID space and read knowledge-base metadata and the document text returned through the retrieval path. The retrieved content is subsequently fed into the LLM chat flow, so the disclosure is of stored corpus data rather than of credentials or system state, which matches the assessed scope of confidentiality-only impact. CVSS 4.0 metrics AT:N (attack requirements: none) and PR:N/UI:N reinforce that no pre-existing session or victim action is assumed by the scoring vector, though a typical IDOR presupposes at least an authenticated tenant context; that discrepancy is the main reason deployment-level auth configuration is the decisive factor here.

Know when Chat Ollama gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (VulnCheck) PRIMARY 8.7 HIGH
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
vuln.today AI 7.5 HIGH

Network-reachable, scriptable sequential-ID enumeration with no interaction; input vector asserts PR:N; impact is read-only data disclosure, so C:H and I:N/A:N.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (VulnCheck).

CVSS VectorVendor: VulnCheck

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
None
Vulnerable system: Availability
None
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

DescriptionCVE.org

ChatOllama through commit 96c3ce5 contains an insecure direct object reference vulnerability that allows remote attackers to access other users' private knowledge bases by supplying sequential ids. Attackers can enumerate ids via GET /api/knowledgebases/{id} or the knowledgebaseId parameter of POST /api/models/chat to read metadata and retrieved document content.

Executive ViewAI

Why It Matters

ChatOllama (sugarforever/chat-ollama) through commit 96c3ce5 contains a high-severity vulnerability that allows unauthenticated attackers to read other users' private knowledge bases, potentially exposing sensitive organizational data and violating tenant isolation. There is no public exploit identified at time of analysis, but the predictable identifier scheme makes the risk of data disclosure significant. Leadership should prioritize mitigation because a breach could lead to regulatory penalties, customer trust erosion, and competitive harm.

Business Impact: High
Compensating Controls

Implement network-level access controls (firewall, VPN, API gateway authentication) to restrict API access; enforce tenant isolation via code modifications; deploy WAF to block sequential ID enumeration; monitor logs for unauthorized access.

Threat Intelligence Overview

EPSS Score
0.4%
Top 65% exploitable
Prevalence
Low
niche self-hosted open-source project, limited production footprint
Data Quality
4 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.4%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
Poc
System Exposure· derived
Open
Automatable
Yes
Human Impact
High
Technical Impact
Partial

Priority Score

44
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +44
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy