<?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>Thu, 08 Oct 2026 15:30:58 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-55013 — Assemblyline 4 Service Client: Arbitrary Write through path traversal in Client code</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2025-55013</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; CybercentreCanada assemblyline&lt;/p&gt;
&lt;p&gt;The Assemblyline 4 Service Client interfaces with the API to fetch tasks and publish the result for a service in Assemblyline 4. In versions below 4.6.1.dev138, the Assemblyline 4 Service Client (task_handler.py) accepts a SHA-256 value returned by the service server and uses it directly as a local file name.A malicious or compromised server (or any MITM that can speak to client) can return a path-traversal payload such as `../../../etc/cron.d/evil` and force the client to write the downloaded bytes to an arbitrary location on disk. This is fixed in version 4.6.1.dev138.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; CybercentreCanada assemblyline&lt;/p&gt;
&lt;p&gt;The Assemblyline 4 Service Client interfaces with the API to fetch tasks and publish the result for a service in Assemblyline 4. In versions below 4.6.1.dev138, the Assemblyline 4 Service Client (task_handler.py) accepts a SHA-256 value returned by the service server and uses it directly as a local file name.A malicious or compromised server (or any MITM that can speak to client) can return a path-traversal payload such as `../../../etc/cron.d/evil` and force the client to write the downloaded bytes to an arbitrary location on disk. This is fixed in version 4.6.1.dev138.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2025-55013</guid>
    </item>
    <item>
      <title>GHSA-75jv-vfxf-3865 — Assemblyline 4 service client vulnerable to Arbitrary Write through path traversal in Client code</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-75jv-vfxf-3865</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: assemblyline-service-client&lt;/p&gt;
&lt;p&gt;**Path-Traversal -&amp;gt; Arbitrary File Write in Assemblyline Service Client**&lt;/p&gt;
&lt;p&gt;**IMPORTANT**: This vulnerability is valid if you decide to use the assemblyline-service-client outside of the normal practice to using Assemblyline in a production environment. In practice, this code should always be executed within a containerized environment such as [assemblyline-v4-service](https://github.com/CybercentreCanada/assemblyline-v4-service) which ensures filesystem-level permissions of what the running user is allowed to access. Furthermore, there is fewer chances for a MiTM compromise when deployed properly in a Docker or Kubernetes deployment where the platform will assign the correct network policies to secure connections between containers instead of relying on the user to set this up manually.&lt;/p&gt;
&lt;p&gt;See https://github.com/CybercentreCanada/assemblyline/issues/382 for further discussion.&lt;/p&gt;
&lt;p&gt;---&lt;/p&gt;
&lt;p&gt;## 1. Summary  
The Assemblyline 4 **service client** (`task_handler.py`) accepts a SHA-256 value returned by the service **server** and uses it directly as a local file name.  
&amp;gt; No validation / sanitisation is performed.&lt;/p&gt;
&lt;p&gt;A **malicious or compromised server** (or any MITM that can speak to client) can return a path-traversal payload such as  
`../../../etc/cron.d/evil`  
and force the client to write the downloaded bytes to an arbitrary location on disk.&lt;/p&gt;
&lt;p&gt;---&lt;/p&gt;
&lt;p&gt;## 2. Affected Versions  
| Item | Value |
|---|---|
| **Component** | `assemblyline-service-client` |
| **Repository** | [CybercentreCana…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: assemblyline-service-client&lt;/p&gt;
&lt;p&gt;**Path-Traversal -&amp;gt; Arbitrary File Write in Assemblyline Service Client**&lt;/p&gt;
&lt;p&gt;**IMPORTANT**: This vulnerability is valid if you decide to use the assemblyline-service-client outside of the normal practice to using Assemblyline in a production environment. In practice, this code should always be executed within a containerized environment such as [assemblyline-v4-service](https://github.com/CybercentreCanada/assemblyline-v4-service) which ensures filesystem-level permissions of what the running user is allowed to access. Furthermore, there is fewer chances for a MiTM compromise when deployed properly in a Docker or Kubernetes deployment where the platform will assign the correct network policies to secure connections between containers instead of relying on the user to set this up manually.&lt;/p&gt;
&lt;p&gt;See https://github.com/CybercentreCanada/assemblyline/issues/382 for further discussion.&lt;/p&gt;
&lt;p&gt;---&lt;/p&gt;
&lt;p&gt;## 1. Summary  
The Assemblyline 4 **service client** (`task_handler.py`) accepts a SHA-256 value returned by the service **server** and uses it directly as a local file name.  
&amp;gt; No validation / sanitisation is performed.&lt;/p&gt;
&lt;p&gt;A **malicious or compromised server** (or any MITM that can speak to client) can return a path-traversal payload such as  
`../../../etc/cron.d/evil`  
and force the client to write the downloaded bytes to an arbitrary location on disk.&lt;/p&gt;
&lt;p&gt;---&lt;/p&gt;
&lt;p&gt;## 2. Affected Versions  
| Item | Value |
|---|---|
| **Component** | `assemblyline-service-client` |
| **Repository** | [CybercentreCana…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-75jv-vfxf-3865</guid>
    </item>
  </channel>
</rss>
