<?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>Mon, 19 Oct 2026 01:55:03 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-158720</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-158720</link>
      <description>EUVD-2026-158720</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-158720</guid>
    </item>
    <item>
      <title>fkie_cve-2024-43373</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-43373</link>
      <description>&lt;p&gt;webcrack is a tool for reverse engineering javascript. An arbitrary file write vulnerability exists in the webcrack module when processing specifically crafted malicious code on Windows systems. This vulnerability is triggered when using the unpack bundles feature in conjunction with the saving feature. If a module name includes a path traversal sequence with Windows path separators, an attacker can exploit this to overwrite files on the host system. This vulnerability allows an attacker to write arbitrary `.js` files to the host system, which can be leveraged to hijack legitimate Node.js modules to gain arbitrary code execution. This vulnerability has been patched in version 2.14.1.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;webcrack is a tool for reverse engineering javascript. An arbitrary file write vulnerability exists in the webcrack module when processing specifically crafted malicious code on Windows systems. This vulnerability is triggered when using the unpack bundles feature in conjunction with the saving feature. If a module name includes a path traversal sequence with Windows path separators, an attacker can exploit this to overwrite files on the host system. This vulnerability allows an attacker to write arbitrary `.js` files to the host system, which can be leveraged to hijack legitimate Node.js modules to gain arbitrary code execution. This vulnerability has been patched in version 2.14.1.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-43373</guid>
    </item>
    <item>
      <title>GHSA-ccqh-278p-xq6w — webcrack has an Arbitrary File Write Vulnerability on Windows when Parsing and Saving a Malicious Bundle</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-ccqh-278p-xq6w</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: webcrack&lt;/p&gt;
&lt;p&gt;### Summary
An arbitrary file write vulnerability exists in the webcrack module when processing specifically crafted malicious code on Windows systems. This vulnerability is triggered when using the unpack bundles feature in conjunction with the saving feature. If a module name includes a path traversal sequence with Windows path separators, an attacker can exploit this to overwrite files on the host system.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;Source: [packages/webcrack/src/unpack/bundle.ts#L79](https://github.com/j4k0xb/webcrack/blob/241f9469e6401f3dabc6373233d85a5e76966b54/packages/webcrack/src/unpack/bundle.ts#L79)
```ts
import { posix } from &amp;#39;node:path&amp;#39;;
import type { Module } from &amp;#39;./module&amp;#39;;&lt;/p&gt;
&lt;p&gt;// eslint-disable-next-line @typescript-eslint/unbound-method
const { dirname, join, normalize } = posix;&lt;/p&gt;
&lt;p&gt;/* ... snip ... */&lt;/p&gt;
&lt;p&gt;const modulePath = normalize(join(path, module.path));
if (!modulePath.startsWith(path)) {
    throw new Error(`detected path traversal: ${module.path}`);
}
await mkdir(dirname(modulePath), {
    recursive: true
});
await writeFile(modulePath, module.code, &amp;#39;utf8&amp;#39;);
```&lt;/p&gt;
&lt;p&gt;In this code, the application explicitly relies on the POSIX version of path utilities (`dirname`, `join`, `normalize`) from Node.js. However, the vulnerability arises because the POSIX version of the `normalize` function does not recognize `\` as a path separator. As a result, on Windows systems, the path traversal check fails, allowing an attacker to write files to unintended locations.&lt;/p&gt;
&lt;p&gt;### PoC
The following…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: webcrack&lt;/p&gt;
&lt;p&gt;### Summary
An arbitrary file write vulnerability exists in the webcrack module when processing specifically crafted malicious code on Windows systems. This vulnerability is triggered when using the unpack bundles feature in conjunction with the saving feature. If a module name includes a path traversal sequence with Windows path separators, an attacker can exploit this to overwrite files on the host system.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;Source: [packages/webcrack/src/unpack/bundle.ts#L79](https://github.com/j4k0xb/webcrack/blob/241f9469e6401f3dabc6373233d85a5e76966b54/packages/webcrack/src/unpack/bundle.ts#L79)
```ts
import { posix } from &amp;#39;node:path&amp;#39;;
import type { Module } from &amp;#39;./module&amp;#39;;&lt;/p&gt;
&lt;p&gt;// eslint-disable-next-line @typescript-eslint/unbound-method
const { dirname, join, normalize } = posix;&lt;/p&gt;
&lt;p&gt;/* ... snip ... */&lt;/p&gt;
&lt;p&gt;const modulePath = normalize(join(path, module.path));
if (!modulePath.startsWith(path)) {
    throw new Error(`detected path traversal: ${module.path}`);
}
await mkdir(dirname(modulePath), {
    recursive: true
});
await writeFile(modulePath, module.code, &amp;#39;utf8&amp;#39;);
```&lt;/p&gt;
&lt;p&gt;In this code, the application explicitly relies on the POSIX version of path utilities (`dirname`, `join`, `normalize`) from Node.js. However, the vulnerability arises because the POSIX version of the `normalize` function does not recognize `\` as a path separator. As a result, on Windows systems, the path traversal check fails, allowing an attacker to write files to unintended locations.&lt;/p&gt;
&lt;p&gt;### PoC
The following…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-ccqh-278p-xq6w</guid>
    </item>
  </channel>
</rss>
