<?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://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-30T11:39:13.298212+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" 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://vulnerability.circl.lu/vuln/cve-2025-31486</id>
    <title>CVE-2025-31486 — Vite allows server.fs.deny to be bypassed with .svg or relative paths</title>
    <updated>2026-09-30T11:39:13.381431+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> vitejs vite</p>
<p>Vite is a frontend tooling framework for javascript. The contents of arbitrary files can be returned to the browser. By adding ?.svg with ?.wasm?init or with sec-fetch-dest: script header, the server.fs.deny restriction was able to bypass. This bypass is only possible if the file is smaller than build.assetsInlineLimit (default: 4kB) and when using Vite 6.0+. Only apps explicitly exposing the Vite dev server to the network (using --host or server.host config option) are affected. This vulnerability is fixed in 4.5.12, 5.4.17, 6.0.14, 6.1.4, and 6.2.5.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2025-31486"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ghsa-xcj6-pq6g-qj4x</id>
    <title>GHSA-xcj6-pq6g-qj4x — Vite allows server.fs.deny to be bypassed with .svg or relative paths</title>
    <updated>2026-09-30T11:39:13.381544+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: vite</p>
<p>### Summary</p>
<p>The contents of arbitrary files can be returned to the browser.</p>
<p>### Impact</p>
<p>Only apps explicitly exposing the Vite dev server to the network (using --host or [server.host config option](https://vitejs.dev/config/server-options.html#server-host)) are affected.</p>
<p>### Details</p>
<p>#### `.svg`</p>
<p>Requests ending with `.svg` are loaded at this line.
https://github.com/vitejs/vite/blob/037f801075ec35bb6e52145d659f71a23813c48f/packages/vite/src/node/plugins/asset.ts#L285-L290
By adding `?.svg` with `?.wasm?init` or with `sec-fetch-dest: script` header, the restriction was able to bypass.</p>
<p>This bypass is only possible if the file is smaller than [`build.assetsInlineLimit`](https://vite.dev/config/build-options.html#build-assetsinlinelimit) (default: 4kB) and when using Vite 6.0+.</p>
<p>#### relative paths</p>
<p>The check was applied before the id normalization. This allowed requests to bypass with relative paths (e.g. `../../`).</p>
<p>### PoC</p>
<p>```bash
npm create vite@latest
cd vite-project/
npm install
npm run dev
```</p>
<p>send request to read `etc/passwd`</p>
<p>```bash
curl 'http://127.0.0.1:5173/etc/passwd?.svg?.wasm?init'
```</p>
<p>```bash
curl 'http://127.0.0.1:5173/@fs/x/x/x/vite-project/?/../../../../../etc/passwd?import&amp;?raw'
```</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ghsa-xcj6-pq6g-qj4x"/>
  </entry>
</feed>
