<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:webfeeds="http://webfeeds.org/rss/1.0"><channel><title>Cpe:2.3:a:chatollama:chatollama:*:*:*:*:*:*:*:* - CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/cpes/cpe2.3achatollamachatollama/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata. Fed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Fri, 16 Oct 2026 18:50:55 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/cpes/cpe2.3achatollamachatollama/feed.xml" rel="self" type="application/rss+xml"/><image><url>https://feed.craftedsignal.io/favicon-32x32.png</url><title>CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/</link><width>32</width><height>32</height></image><webfeeds:icon>https://feed.craftedsignal.io/favicon.svg</webfeeds:icon><item><title>CVE-2026-111702: Insecure Direct Object Reference in ChatOllama</title><link>https://feed.craftedsignal.io/briefs/2026-10-chatollama-idor/</link><pubDate>Fri, 16 Oct 2026 18:50:55 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-10-chatollama-idor/</guid><description>ChatOllama through commit 96c3ce5 contains an insecure direct object reference vulnerability that allows unauthenticated attackers to access private knowledge bases by enumerating sequential ID values.</description><content:encoded><![CDATA[<p>ChatOllama through commit 96c3ce5 is affected by an insecure direct object reference (IDOR) vulnerability, tracked as CVE-2026-111702. This vulnerability allows remote, unauthenticated attackers to bypass authorization controls and access private knowledge bases stored within the application. By providing sequential numerical identifiers to the API, an attacker can enumerate and retrieve sensitive metadata and the content of documents associated with other users' knowledge bases. The vulnerability resides in how the application processes the {id} parameter in GET requests to the knowledgebase endpoint and the knowledgebaseId parameter in POST requests to the chat model interface. Given that these endpoints are typically exposed for API interaction, this flaw poses a significant risk to the confidentiality of organizational data processed by the ChatOllama platform.</p>
<h2 id="impact">Impact</h2>
<p>Successful exploitation of this vulnerability leads to unauthorized access and exfiltration of sensitive information stored within ChatOllama knowledge bases. As knowledge bases often contain internal documentation, private datasets, or proprietary information, this exposure can result in significant data breaches, potential compliance violations, and loss of intellectual property. Since the identifiers are sequential, an attacker can systematically scrape the entire knowledge base repository of an instance without requiring specific knowledge of existing IDs.</p>
<h2 id="recommendation">Recommendation</h2>
<p>Update ChatOllama installations to a version beyond commit 96c3ce5 once a security patch is provided by the vendor. In the interim, implement strict network-level access controls for the /api/knowledgebases and /api/models/chat endpoints to restrict traffic to known, trusted internal IP ranges.</p>
<h2 id="detection">Detection</h2>
<p>Because this vulnerability relies on sequential ID enumeration, detection teams should monitor web access logs for anomalous spikes in 200 OK responses from the /api/knowledgebases/ endpoint, specifically looking for high counts of distinct requested IDs originating from a single source IP.</p>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>web-application-vulnerability</category><category>idor</category><category>cve-2026-111702</category></item></channel></rss>