<?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://vulnerability.circl.lu</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>Thu, 01 Oct 2026 07:34:56 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-44843 — LangChain: Unsafe deserialization of attacker-controlled LangChain objects through overly broad `load()` allowlists</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-44843</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; langchain-ai langchain&lt;/p&gt;
&lt;p&gt;LangChain is a framework for building agents and LLM-powered applications. Prior to 0.3.85 and 1.3.3, LangChain contains older runtime code paths that deserialize run inputs, run outputs, or other application-controlled payloads using overly broad object allowlists. These paths may call load() with allowed_objects=&amp;#34;all&amp;#34;. This does not enable arbitrary Python object deserialization, but it does allow any trusted LangChain-serializable object to be revived, which is broader than these runtime paths require. As a result, attacker-supplied LangChain serialized constructor dictionaries may cause trusted runtime paths to instantiate classes with untrusted constructor arguments. This vulnerability is fixed in 0.3.85 and 1.3.3.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; langchain-ai langchain&lt;/p&gt;
&lt;p&gt;LangChain is a framework for building agents and LLM-powered applications. Prior to 0.3.85 and 1.3.3, LangChain contains older runtime code paths that deserialize run inputs, run outputs, or other application-controlled payloads using overly broad object allowlists. These paths may call load() with allowed_objects=&amp;#34;all&amp;#34;. This does not enable arbitrary Python object deserialization, but it does allow any trusted LangChain-serializable object to be revived, which is broader than these runtime paths require. As a result, attacker-supplied LangChain serialized constructor dictionaries may cause trusted runtime paths to instantiate classes with untrusted constructor arguments. This vulnerability is fixed in 0.3.85 and 1.3.3.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-44843</guid>
    </item>
    <item>
      <title>GHSA-pjwx-r37v-7724 — LangChain vulnerable to unsafe deserialization of attacker-controlled objects through overly broad `load()` allowlists</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-pjwx-r37v-7724</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: langchain-core&lt;/p&gt;
&lt;p&gt;LangChain contains older runtime code paths that deserialize run inputs, run outputs, or other application-controlled payloads using overly broad object allowlists. These paths may call `load()` with `allowed_objects=&amp;#34;all&amp;#34;`. This does not enable arbitrary Python object deserialization, but it does allow any trusted LangChain-serializable object to be revived, which is broader than these runtime paths require. As a result, attacker-supplied LangChain serialized constructor dictionaries may cause trusted runtime paths to instantiate classes with untrusted constructor arguments.&lt;/p&gt;
&lt;p&gt;Applications are exposed only when all of the following are true:&lt;/p&gt;
&lt;p&gt;1. The application accepts untrusted structured input, such as JSON, from a user or network request.
2. The application does not validate or canonicalize that input into an inert schema before invoking LangChain.
3. Attacker-controlled nested dictionaries or lists are preserved in LangChain run inputs or outputs.
4. The application uses an affected API path that later deserializes that run data.&lt;/p&gt;
&lt;p&gt;Known affected runtime surfaces include:&lt;/p&gt;
&lt;p&gt;- `RunnableWithMessageHistory`
- `astream_log()`
- `astream_events(version=&amp;#34;v1&amp;#34;)`&lt;/p&gt;
&lt;p&gt;Related unsafe deserialization patterns may also affect applications that explicitly load serialized LangChain prompt or runnable objects from untrusted sources, including shared prompt stores, Hub artifacts with model configuration, or other application-controlled serialization stores.&lt;/p&gt;
&lt;p&gt;Applications that validate incomin…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: langchain-core&lt;/p&gt;
&lt;p&gt;LangChain contains older runtime code paths that deserialize run inputs, run outputs, or other application-controlled payloads using overly broad object allowlists. These paths may call `load()` with `allowed_objects=&amp;#34;all&amp;#34;`. This does not enable arbitrary Python object deserialization, but it does allow any trusted LangChain-serializable object to be revived, which is broader than these runtime paths require. As a result, attacker-supplied LangChain serialized constructor dictionaries may cause trusted runtime paths to instantiate classes with untrusted constructor arguments.&lt;/p&gt;
&lt;p&gt;Applications are exposed only when all of the following are true:&lt;/p&gt;
&lt;p&gt;1. The application accepts untrusted structured input, such as JSON, from a user or network request.
2. The application does not validate or canonicalize that input into an inert schema before invoking LangChain.
3. Attacker-controlled nested dictionaries or lists are preserved in LangChain run inputs or outputs.
4. The application uses an affected API path that later deserializes that run data.&lt;/p&gt;
&lt;p&gt;Known affected runtime surfaces include:&lt;/p&gt;
&lt;p&gt;- `RunnableWithMessageHistory`
- `astream_log()`
- `astream_events(version=&amp;#34;v1&amp;#34;)`&lt;/p&gt;
&lt;p&gt;Related unsafe deserialization patterns may also affect applications that explicitly load serialized LangChain prompt or runnable objects from untrusted sources, including shared prompt stores, Hub artifacts with model configuration, or other application-controlled serialization stores.&lt;/p&gt;
&lt;p&gt;Applications that validate incomin…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-pjwx-r37v-7724</guid>
    </item>
    <item>
      <title>PYSEC-2026-2564 — LangChain vulnerable to unsafe deserialization of attacker-controlled objects through overly broad `load()` allowlists</title>
      <link>https://vulnerability.circl.lu/vuln/pysec-2026-2564</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: langchain-core&lt;/p&gt;
&lt;p&gt;LangChain contains older runtime code paths that deserialize run inputs, run outputs, or other application-controlled payloads using overly broad object allowlists. These paths may call `load()` with `allowed_objects=&amp;#34;all&amp;#34;`. This does not enable arbitrary Python object deserialization, but it does allow any trusted LangChain-serializable object to be revived, which is broader than these runtime paths require. As a result, attacker-supplied LangChain serialized constructor dictionaries may cause trusted runtime paths to instantiate classes with untrusted constructor arguments.&lt;/p&gt;
&lt;p&gt;Applications are exposed only when all of the following are true:&lt;/p&gt;
&lt;p&gt;1. The application accepts untrusted structured input, such as JSON, from a user or network request.
2. The application does not validate or canonicalize that input into an inert schema before invoking LangChain.
3. Attacker-controlled nested dictionaries or lists are preserved in LangChain run inputs or outputs.
4. The application uses an affected API path that later deserializes that run data.&lt;/p&gt;
&lt;p&gt;Known affected runtime surfaces include:&lt;/p&gt;
&lt;p&gt;- `RunnableWithMessageHistory`
- `astream_log()`
- `astream_events(version=&amp;#34;v1&amp;#34;)`&lt;/p&gt;
&lt;p&gt;Related unsafe deserialization patterns may also affect applications that explicitly load serialized LangChain prompt or runnable objects from untrusted sources, including shared prompt stores, Hub artifacts with model configuration, or other application-controlled serialization stores.&lt;/p&gt;
&lt;p&gt;Applications that validate incomin…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: langchain-core&lt;/p&gt;
&lt;p&gt;LangChain contains older runtime code paths that deserialize run inputs, run outputs, or other application-controlled payloads using overly broad object allowlists. These paths may call `load()` with `allowed_objects=&amp;#34;all&amp;#34;`. This does not enable arbitrary Python object deserialization, but it does allow any trusted LangChain-serializable object to be revived, which is broader than these runtime paths require. As a result, attacker-supplied LangChain serialized constructor dictionaries may cause trusted runtime paths to instantiate classes with untrusted constructor arguments.&lt;/p&gt;
&lt;p&gt;Applications are exposed only when all of the following are true:&lt;/p&gt;
&lt;p&gt;1. The application accepts untrusted structured input, such as JSON, from a user or network request.
2. The application does not validate or canonicalize that input into an inert schema before invoking LangChain.
3. Attacker-controlled nested dictionaries or lists are preserved in LangChain run inputs or outputs.
4. The application uses an affected API path that later deserializes that run data.&lt;/p&gt;
&lt;p&gt;Known affected runtime surfaces include:&lt;/p&gt;
&lt;p&gt;- `RunnableWithMessageHistory`
- `astream_log()`
- `astream_events(version=&amp;#34;v1&amp;#34;)`&lt;/p&gt;
&lt;p&gt;Related unsafe deserialization patterns may also affect applications that explicitly load serialized LangChain prompt or runnable objects from untrusted sources, including shared prompt stores, Hub artifacts with model configuration, or other application-controlled serialization stores.&lt;/p&gt;
&lt;p&gt;Applications that validate incomin…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/pysec-2026-2564</guid>
    </item>
  </channel>
</rss>
