<?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>Sat, 03 Oct 2026 05:21:04 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-62703 — Fugue is Vulnerable to Remote Code Execution by Pickle Deserialization via FlaskRPCServer</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-62703</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; fugue-project fugue&lt;/p&gt;
&lt;p&gt;Fugue is a unified interface for distributed computing that lets users execute Python, Pandas, and SQL code on Spark, Dask, and Ray with minimal rewrites. In version 0.9.2 and prior, there is a remote code execution vulnerability by pickle deserialization via FlaskRPCServer. The Fugue framework implements an RPC server system for distributed computing operations. In the core functionality of the RPC server implementation, I found that the _decode() function in fugue/rpc/flask.py directly uses cloudpickle.loads() to deserialize data without any sanitization. This creates a remote code execution vulnerability when malicious pickle data is processed by the RPC server. The vulnerability exists in the RPC communication mechanism where the client can send arbitrary serialized Python objects that will be deserialized on the server side, allowing attackers to execute arbitrary code on the victim&amp;#39;s machine. This issue has been patched via commit 6f25326.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; fugue-project fugue&lt;/p&gt;
&lt;p&gt;Fugue is a unified interface for distributed computing that lets users execute Python, Pandas, and SQL code on Spark, Dask, and Ray with minimal rewrites. In version 0.9.2 and prior, there is a remote code execution vulnerability by pickle deserialization via FlaskRPCServer. The Fugue framework implements an RPC server system for distributed computing operations. In the core functionality of the RPC server implementation, I found that the _decode() function in fugue/rpc/flask.py directly uses cloudpickle.loads() to deserialize data without any sanitization. This creates a remote code execution vulnerability when malicious pickle data is processed by the RPC server. The vulnerability exists in the RPC communication mechanism where the client can send arbitrary serialized Python objects that will be deserialized on the server side, allowing attackers to execute arbitrary code on the victim&amp;#39;s machine. This issue has been patched via commit 6f25326.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-62703</guid>
    </item>
    <item>
      <title>GHSA-xv5p-fjw5-vrj6 — Fugue is Vulnerable to Remote Code Execution by Pickle Deserialization via FlaskRPCServer</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-xv5p-fjw5-vrj6</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: fugue&lt;/p&gt;
&lt;p&gt;### Summary
The Fugue framework implements an RPC server system for distributed computing operations. In the core functionality of the RPC server implementation, I found that the _decode() function in fugue/rpc/flask.py directly uses cloudpickle.loads() to deserialize data without any sanitization. This creates a remote code execution vulnerability when malicious pickle data is processed by the RPC server.The vulnerability exists in the RPC communication mechanism where the client can send arbitrary serialized Python objects that will be deserialized on the server side, allowing attackers to execute arbitrary code on the victim&amp;#39;s machine.&lt;/p&gt;
&lt;p&gt;### Details
_decode() function in fugue/rpc/flask.py directly uses cloudpickle.loads() to deserialize data without any sanitization.&lt;/p&gt;
&lt;p&gt;### PoC
* Step1:
The victim user starts an RPC server binding to open network using the Fugue framework. Here, I use the official RPC server code to initialize the server.&lt;/p&gt;
&lt;p&gt;* Step2:
The attacker modifies the _encode() function in fugue/rpc/flask.py to inject malicious pickle data:&lt;/p&gt;
&lt;p&gt;&amp;lt;img width=&amp;#34;740&amp;#34; height=&amp;#34;260&amp;#34; alt=&amp;#34;image&amp;#34; src=&amp;#34;https://github.com/user-attachments/assets/6064516b-e1a6-45fa-a91c-8e276bc4a106&amp;#34; /&amp;gt;&lt;/p&gt;
&lt;p&gt;In this example, attacker modifies _encode to let the victim execute command “ls -l”&lt;/p&gt;
&lt;p&gt;* Step 3:
The attacker then uses the RPC client to send the malicious request&lt;/p&gt;
&lt;p&gt;Fugue gives a demo video and the PoC in the attachment, along with modified flask.py. When users reproduce this issue, in the server sid…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: fugue&lt;/p&gt;
&lt;p&gt;### Summary
The Fugue framework implements an RPC server system for distributed computing operations. In the core functionality of the RPC server implementation, I found that the _decode() function in fugue/rpc/flask.py directly uses cloudpickle.loads() to deserialize data without any sanitization. This creates a remote code execution vulnerability when malicious pickle data is processed by the RPC server.The vulnerability exists in the RPC communication mechanism where the client can send arbitrary serialized Python objects that will be deserialized on the server side, allowing attackers to execute arbitrary code on the victim&amp;#39;s machine.&lt;/p&gt;
&lt;p&gt;### Details
_decode() function in fugue/rpc/flask.py directly uses cloudpickle.loads() to deserialize data without any sanitization.&lt;/p&gt;
&lt;p&gt;### PoC
* Step1:
The victim user starts an RPC server binding to open network using the Fugue framework. Here, I use the official RPC server code to initialize the server.&lt;/p&gt;
&lt;p&gt;* Step2:
The attacker modifies the _encode() function in fugue/rpc/flask.py to inject malicious pickle data:&lt;/p&gt;
&lt;p&gt;&amp;lt;img width=&amp;#34;740&amp;#34; height=&amp;#34;260&amp;#34; alt=&amp;#34;image&amp;#34; src=&amp;#34;https://github.com/user-attachments/assets/6064516b-e1a6-45fa-a91c-8e276bc4a106&amp;#34; /&amp;gt;&lt;/p&gt;
&lt;p&gt;In this example, attacker modifies _encode to let the victim execute command “ls -l”&lt;/p&gt;
&lt;p&gt;* Step 3:
The attacker then uses the RPC client to send the malicious request&lt;/p&gt;
&lt;p&gt;Fugue gives a demo video and the PoC in the attachment, along with modified flask.py. When users reproduce this issue, in the server sid…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-xv5p-fjw5-vrj6</guid>
    </item>
  </channel>
</rss>
