<?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>Tue, 06 Oct 2026 10:24:02 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-218521</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-218521</link>
      <description>EUVD-2026-218521</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-218521</guid>
    </item>
    <item>
      <title>fkie_cve-2025-27098</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-27098</link>
      <description>&lt;p&gt;GraphQL Mesh is a GraphQL Federation framework and gateway for both GraphQL Federation and non-GraphQL Federation subgraphs, non-GraphQL services, such as REST and gRPC, and also databases such as MongoDB, MySQL, and PostgreSQL. Missing check vulnerability in the static file handler allows any client to access the files in the server&amp;#39;s file system. When `staticFiles` is set in the `serve` settings in the configuration file, the following handler doesn&amp;#39;t check if `absolutePath` is still under the directory provided as `staticFiles`. Users have two options to fix vulnerability; 1. Update `@graphql-mesh/cli` to a version higher than `0.82.21`, and if you use `@graphql-mesh/http`, update it to a version higher than `0.3.18` 2. Remove `staticFiles` option from the configuration, and use other solutions to serve static files.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;GraphQL Mesh is a GraphQL Federation framework and gateway for both GraphQL Federation and non-GraphQL Federation subgraphs, non-GraphQL services, such as REST and gRPC, and also databases such as MongoDB, MySQL, and PostgreSQL. Missing check vulnerability in the static file handler allows any client to access the files in the server&amp;#39;s file system. When `staticFiles` is set in the `serve` settings in the configuration file, the following handler doesn&amp;#39;t check if `absolutePath` is still under the directory provided as `staticFiles`. Users have two options to fix vulnerability; 1. Update `@graphql-mesh/cli` to a version higher than `0.82.21`, and if you use `@graphql-mesh/http`, update it to a version higher than `0.3.18` 2. Remove `staticFiles` option from the configuration, and use other solutions to serve static files.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-27098</guid>
    </item>
    <item>
      <title>GHSA-j2wh-wrv3-4x4g — Unwanted access to the entire file system vulnerability due to a missing check in `staticFiles` HTTP handler</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-j2wh-wrv3-4x4g</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: @graphql-mesh/cli, npm: @graphql-mesh/http&lt;/p&gt;
&lt;p&gt;### Summary
Missing check vulnerability in the static file handler allows any client to access the files in the server&amp;#39;s file system&lt;/p&gt;
&lt;p&gt;### Details
When `staticFiles` is set in the `serve` settings in the configuration file, the following handler doesn&amp;#39;t check if `absolutePath` is still under the directory provided as `staticFiles`;&lt;/p&gt;
&lt;p&gt;```ts
  if (staticFiles) {
    router.get(&amp;#39;/:relativePath+&amp;#39;, async request =&amp;gt; {
      let { relativePath } = request.params;
      if (!relativePath) {
        relativePath = &amp;#39;index.html&amp;#39;;
      }
      const absolutePath = path.join(baseDir, staticFiles, relativePath);
      if (absolutePath.includes(staticFiles) &amp;amp;&amp;amp; (await pathExists(absolutePath))) {
        const readStream = fs.createReadStream(absolutePath);
        return new Response(readStream as any, {
          status: 200,
        });
      }
      return undefined;
    });
 ```&lt;/p&gt;
&lt;p&gt;### Example scenario
To reproduce it, set `staticFiles` to the relative path of a directory in `.meshrc.yml`;&lt;/p&gt;
&lt;p&gt;```yml
serve:
   staticFiles: ./public
```&lt;/p&gt;
&lt;p&gt;Then start the server with `mesh dev`, and browse to `/..%2fpackage.json` then you will see the content of `package.json`. You can even go deeper to see sensitive data; `/..%2f..%2f..%2f..%2f..%2f..%2f..%2f..%2f..%2f..%2f..%2f..%2fetc/passwd`&lt;/p&gt;
&lt;p&gt;### Impact and solution
If `staticFiles` is set under `serve` in the configuration file. you have two options to fix vulnerability;&lt;/p&gt;
&lt;p&gt;- Update `@graphql-mesh/cli` to a version higher than `0.82.21`, and if you use `@grap…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: @graphql-mesh/cli, npm: @graphql-mesh/http&lt;/p&gt;
&lt;p&gt;### Summary
Missing check vulnerability in the static file handler allows any client to access the files in the server&amp;#39;s file system&lt;/p&gt;
&lt;p&gt;### Details
When `staticFiles` is set in the `serve` settings in the configuration file, the following handler doesn&amp;#39;t check if `absolutePath` is still under the directory provided as `staticFiles`;&lt;/p&gt;
&lt;p&gt;```ts
  if (staticFiles) {
    router.get(&amp;#39;/:relativePath+&amp;#39;, async request =&amp;gt; {
      let { relativePath } = request.params;
      if (!relativePath) {
        relativePath = &amp;#39;index.html&amp;#39;;
      }
      const absolutePath = path.join(baseDir, staticFiles, relativePath);
      if (absolutePath.includes(staticFiles) &amp;amp;&amp;amp; (await pathExists(absolutePath))) {
        const readStream = fs.createReadStream(absolutePath);
        return new Response(readStream as any, {
          status: 200,
        });
      }
      return undefined;
    });
 ```&lt;/p&gt;
&lt;p&gt;### Example scenario
To reproduce it, set `staticFiles` to the relative path of a directory in `.meshrc.yml`;&lt;/p&gt;
&lt;p&gt;```yml
serve:
   staticFiles: ./public
```&lt;/p&gt;
&lt;p&gt;Then start the server with `mesh dev`, and browse to `/..%2fpackage.json` then you will see the content of `package.json`. You can even go deeper to see sensitive data; `/..%2f..%2f..%2f..%2f..%2f..%2f..%2f..%2f..%2f..%2f..%2f..%2fetc/passwd`&lt;/p&gt;
&lt;p&gt;### Impact and solution
If `staticFiles` is set under `serve` in the configuration file. you have two options to fix vulnerability;&lt;/p&gt;
&lt;p&gt;- Update `@graphql-mesh/cli` to a version higher than `0.82.21`, and if you use `@grap…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-j2wh-wrv3-4x4g</guid>
    </item>
  </channel>
</rss>
