<?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, 17 Oct 2026 12:31:09 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-260404</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-260404</link>
      <description>EUVD-2026-260404</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-260404</guid>
    </item>
    <item>
      <title>fkie_cve-2025-64439</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-64439</link>
      <description>&lt;p&gt;LangGraph SQLite Checkpoint is an implementation of LangGraph CheckpointSaver that uses SQLite DB (both sync and async, via aiosqlite). In versions 2.1.2 and below, the JsonPlusSerializer (used as the default serialization protocol for all checkpointing) contains a Remote Code Execution (RCE) vulnerability when deserializing payloads saved in the &amp;#34;json&amp;#34; serialization mode. By default, the serializer attempts to use &amp;#34;msgpack&amp;#34; for serialization. However, prior to version 3.0 of the checkpointer library, if illegal Unicode surrogate values caused serialization to fail, it would fall back to using the &amp;#34;json&amp;#34; mode. This issue is fixed in version 3.0.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;LangGraph SQLite Checkpoint is an implementation of LangGraph CheckpointSaver that uses SQLite DB (both sync and async, via aiosqlite). In versions 2.1.2 and below, the JsonPlusSerializer (used as the default serialization protocol for all checkpointing) contains a Remote Code Execution (RCE) vulnerability when deserializing payloads saved in the &amp;#34;json&amp;#34; serialization mode. By default, the serializer attempts to use &amp;#34;msgpack&amp;#34; for serialization. However, prior to version 3.0 of the checkpointer library, if illegal Unicode surrogate values caused serialization to fail, it would fall back to using the &amp;#34;json&amp;#34; mode. This issue is fixed in version 3.0.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-64439</guid>
    </item>
    <item>
      <title>GHSA-wwqv-p2pp-99h5 — LangGraph Checkpoint affected by RCE in "json" mode of JsonPlusSerializer</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-wwqv-p2pp-99h5</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: langgraph-checkpoint&lt;/p&gt;
&lt;p&gt;# Summary&lt;/p&gt;
&lt;p&gt;Prior to `langgraph-checkpoint` version `3.0` , LangGraph’s `JsonPlusSerializer` (used as the default serialization protocol for all checkpointing) contains a remote code execution (RCE) vulnerability when deserializing payloads saved in the `&amp;#34;json&amp;#34;` serialization mode.&lt;/p&gt;
&lt;p&gt;If an attacker can cause your application to persist a payload serialized in this mode, they may be able to also send malicious content that executes arbitrary Python code during deserialization.&lt;/p&gt;
&lt;p&gt;Upgrading to version langgraph-checkpoint `3.0` patches this vulnerability by preventing deserialization of custom objects saved in this mode.&lt;/p&gt;
&lt;p&gt;If you are deploying in `langgraph-api`, any version `0.5` or later is also free of this vulnerability.&lt;/p&gt;
&lt;p&gt;# Details&lt;/p&gt;
&lt;p&gt;**Affected file / component**&lt;/p&gt;
&lt;p&gt;[jsonplus.py](https://github.com/langchain-ai/langgraph/blob/c5744f583b11745cd406f3059903e17bbcdcc8ac/libs/checkpoint/langgraph/checkpoint/serde/jsonplus.py)&lt;/p&gt;
&lt;p&gt;By default, the serializer attempts to use `&amp;#34;msgpack&amp;#34;` for serialization. However, prior to version `3.0` of the checkpointer library, if illegal Unicode surrogate values caused serialization to fail,  it would fall back to using the `&amp;#34;json&amp;#34;` mode.&lt;/p&gt;
&lt;p&gt;When operating in this mode, the deserializer supports a constructor-style format (`lc == 2`, `type == &amp;#34;constructor&amp;#34;`) for custom objects to allow them to be reconstructed at load time.  If an attacker is able to trigger this mode with a malicious payload, deserializing  allow the attacker to execute arbitrary functi…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: langgraph-checkpoint&lt;/p&gt;
&lt;p&gt;# Summary&lt;/p&gt;
&lt;p&gt;Prior to `langgraph-checkpoint` version `3.0` , LangGraph’s `JsonPlusSerializer` (used as the default serialization protocol for all checkpointing) contains a remote code execution (RCE) vulnerability when deserializing payloads saved in the `&amp;#34;json&amp;#34;` serialization mode.&lt;/p&gt;
&lt;p&gt;If an attacker can cause your application to persist a payload serialized in this mode, they may be able to also send malicious content that executes arbitrary Python code during deserialization.&lt;/p&gt;
&lt;p&gt;Upgrading to version langgraph-checkpoint `3.0` patches this vulnerability by preventing deserialization of custom objects saved in this mode.&lt;/p&gt;
&lt;p&gt;If you are deploying in `langgraph-api`, any version `0.5` or later is also free of this vulnerability.&lt;/p&gt;
&lt;p&gt;# Details&lt;/p&gt;
&lt;p&gt;**Affected file / component**&lt;/p&gt;
&lt;p&gt;[jsonplus.py](https://github.com/langchain-ai/langgraph/blob/c5744f583b11745cd406f3059903e17bbcdcc8ac/libs/checkpoint/langgraph/checkpoint/serde/jsonplus.py)&lt;/p&gt;
&lt;p&gt;By default, the serializer attempts to use `&amp;#34;msgpack&amp;#34;` for serialization. However, prior to version `3.0` of the checkpointer library, if illegal Unicode surrogate values caused serialization to fail,  it would fall back to using the `&amp;#34;json&amp;#34;` mode.&lt;/p&gt;
&lt;p&gt;When operating in this mode, the deserializer supports a constructor-style format (`lc == 2`, `type == &amp;#34;constructor&amp;#34;`) for custom objects to allow them to be reconstructed at load time.  If an attacker is able to trigger this mode with a malicious payload, deserializing  allow the attacker to execute arbitrary functi…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-wwqv-p2pp-99h5</guid>
    </item>
    <item>
      <title>PYSEC-2026-1527 — LangGraph Checkpoint affected by RCE in "json" mode of JsonPlusSerializer</title>
      <link>https://cve.radiocsirt.org/vuln/pysec-2026-1527</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: langgraph-checkpoint&lt;/p&gt;
&lt;p&gt;# Summary&lt;/p&gt;
&lt;p&gt;Prior to `langgraph-checkpoint` version `3.0` , LangGraph’s `JsonPlusSerializer` (used as the default serialization protocol for all checkpointing) contains a remote code execution (RCE) vulnerability when deserializing payloads saved in the `&amp;#34;json&amp;#34;` serialization mode.&lt;/p&gt;
&lt;p&gt;If an attacker can cause your application to persist a payload serialized in this mode, they may be able to also send malicious content that executes arbitrary Python code during deserialization.&lt;/p&gt;
&lt;p&gt;Upgrading to version langgraph-checkpoint `3.0` patches this vulnerability by preventing deserialization of custom objects saved in this mode.&lt;/p&gt;
&lt;p&gt;If you are deploying in `langgraph-api`, any version `0.5` or later is also free of this vulnerability.&lt;/p&gt;
&lt;p&gt;# Details&lt;/p&gt;
&lt;p&gt;**Affected file / component**&lt;/p&gt;
&lt;p&gt;[jsonplus.py](https://github.com/langchain-ai/langgraph/blob/c5744f583b11745cd406f3059903e17bbcdcc8ac/libs/checkpoint/langgraph/checkpoint/serde/jsonplus.py)&lt;/p&gt;
&lt;p&gt;By default, the serializer attempts to use `&amp;#34;msgpack&amp;#34;` for serialization. However, prior to version `3.0` of the checkpointer library, if illegal Unicode surrogate values caused serialization to fail,  it would fall back to using the `&amp;#34;json&amp;#34;` mode.&lt;/p&gt;
&lt;p&gt;When operating in this mode, the deserializer supports a constructor-style format (`lc == 2`, `type == &amp;#34;constructor&amp;#34;`) for custom objects to allow them to be reconstructed at load time.  If an attacker is able to trigger this mode with a malicious payload, deserializing  allow the attacker to execute arbitrary functi…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: langgraph-checkpoint&lt;/p&gt;
&lt;p&gt;# Summary&lt;/p&gt;
&lt;p&gt;Prior to `langgraph-checkpoint` version `3.0` , LangGraph’s `JsonPlusSerializer` (used as the default serialization protocol for all checkpointing) contains a remote code execution (RCE) vulnerability when deserializing payloads saved in the `&amp;#34;json&amp;#34;` serialization mode.&lt;/p&gt;
&lt;p&gt;If an attacker can cause your application to persist a payload serialized in this mode, they may be able to also send malicious content that executes arbitrary Python code during deserialization.&lt;/p&gt;
&lt;p&gt;Upgrading to version langgraph-checkpoint `3.0` patches this vulnerability by preventing deserialization of custom objects saved in this mode.&lt;/p&gt;
&lt;p&gt;If you are deploying in `langgraph-api`, any version `0.5` or later is also free of this vulnerability.&lt;/p&gt;
&lt;p&gt;# Details&lt;/p&gt;
&lt;p&gt;**Affected file / component**&lt;/p&gt;
&lt;p&gt;[jsonplus.py](https://github.com/langchain-ai/langgraph/blob/c5744f583b11745cd406f3059903e17bbcdcc8ac/libs/checkpoint/langgraph/checkpoint/serde/jsonplus.py)&lt;/p&gt;
&lt;p&gt;By default, the serializer attempts to use `&amp;#34;msgpack&amp;#34;` for serialization. However, prior to version `3.0` of the checkpointer library, if illegal Unicode surrogate values caused serialization to fail,  it would fall back to using the `&amp;#34;json&amp;#34;` mode.&lt;/p&gt;
&lt;p&gt;When operating in this mode, the deserializer supports a constructor-style format (`lc == 2`, `type == &amp;#34;constructor&amp;#34;`) for custom objects to allow them to be reconstructed at load time.  If an attacker is able to trigger this mode with a malicious payload, deserializing  allow the attacker to execute arbitrary functi…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/pysec-2026-1527</guid>
    </item>
  </channel>
</rss>
