<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Sat, 10 Oct 2026 14:55:42 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-106119 — LangChain: MongoDBChatMessageHistory query injection can allow cross-session access</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-106119</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; langchain-ai langchainjs, @langchain mongodb&lt;/p&gt;
&lt;p&gt;LangChain is a framework for building LLM-powered applications. Prior to 1.3.1, MongoDBChatMessageHistory does not enforce the documented string type for an untrusted structured session identifier at runtime, allowing the identifier to be interpreted as a MongoDB query condition rather than as a literal value when multiple users&amp;#39; histories are stored in a shared MongoDB collection. An attacker able to invoke chat-history operations can read, modify, or delete another user&amp;#39;s stored conversation. Applications using authenticated, server-controlled string identifiers are not affected. This issue is fixed in version 1.3.1.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; langchain-ai langchainjs, @langchain mongodb&lt;/p&gt;
&lt;p&gt;LangChain is a framework for building LLM-powered applications. Prior to 1.3.1, MongoDBChatMessageHistory does not enforce the documented string type for an untrusted structured session identifier at runtime, allowing the identifier to be interpreted as a MongoDB query condition rather than as a literal value when multiple users&amp;#39; histories are stored in a shared MongoDB collection. An attacker able to invoke chat-history operations can read, modify, or delete another user&amp;#39;s stored conversation. Applications using authenticated, server-controlled string identifiers are not affected. This issue is fixed in version 1.3.1.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-106119</guid>
    </item>
  </channel>
</rss>
