<?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>Sun, 18 Oct 2026 05:42:00 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-209249</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-209249</link>
      <description>EUVD-2026-209249</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-209249</guid>
    </item>
    <item>
      <title>fkie_cve-2023-34238</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2023-34238</link>
      <description>&lt;p&gt;Gatsby is a free and open source framework based on React. The Gatsby framework prior to versions 4.25.7 and 5.9.1 contain a Local File Inclusion vulnerability in the `__file-code-frame` and `__original-stack-frame` paths, exposed when running the Gatsby develop server (`gatsby develop`). Any file in scope of the development server could potentially be exposed. It should be noted that by default `gatsby develop` is only accessible via the localhost `127.0.0.1`, and one would need to intentionally expose the server to other interfaces to exploit this vulnerability by using server options such as `--host 0.0.0.0`, `-H 0.0.0.0`, or the `GATSBY_HOST=0.0.0.0` environment variable. A patch has been introduced in `gatsby@5.9.1` and `gatsby@4.25.7` which mitigates the issue. Users are advised to upgrade. Users unable to upgrade should avoid exposing their development server to the internet.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Gatsby is a free and open source framework based on React. The Gatsby framework prior to versions 4.25.7 and 5.9.1 contain a Local File Inclusion vulnerability in the `__file-code-frame` and `__original-stack-frame` paths, exposed when running the Gatsby develop server (`gatsby develop`). Any file in scope of the development server could potentially be exposed. It should be noted that by default `gatsby develop` is only accessible via the localhost `127.0.0.1`, and one would need to intentionally expose the server to other interfaces to exploit this vulnerability by using server options such as `--host 0.0.0.0`, `-H 0.0.0.0`, or the `GATSBY_HOST=0.0.0.0` environment variable. A patch has been introduced in `gatsby@5.9.1` and `gatsby@4.25.7` which mitigates the issue. Users are advised to upgrade. Users unable to upgrade should avoid exposing their development server to the internet.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2023-34238</guid>
    </item>
    <item>
      <title>GHSA-c6f8-8r25-c4gc — Gatsby develop server has Local File Inclusion vulnerability</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-c6f8-8r25-c4gc</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: gatsby&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;The Gatsby framework prior to versions 4.25.7 and 5.9.1 contain a Local File Inclusion vulnerability in the `__file-code-frame` and `__original-stack-frame` paths, exposed when running the Gatsby develop server (`gatsby develop`).&lt;/p&gt;
&lt;p&gt;The following steps can be used to reproduce the vulnerability:&lt;/p&gt;
&lt;p&gt;```
# Create a new Gatsby project
$ npm init gatsby
$ cd my-gatsby-site&lt;/p&gt;
&lt;p&gt;# Start the Gatsby develop server
$ gatsby develop&lt;/p&gt;
&lt;p&gt;# Execute the Local File Inclusion vulnerability in __file-code-frame
$ curl &amp;#34;http://127.0.0.1:8000/__file-code-frame?filePath=/etc/passwd&amp;amp;lineNumber=1&amp;#34;&lt;/p&gt;
&lt;p&gt;# Execute the Local File Inclusion vulnerability in __original-stack-frame
$ curl &amp;#34;http://127.0.0.1:8000/__original-stack-frame?moduleId=/etc/hosts&amp;amp;lineNumber=1&amp;amp;skipSourceMap=1&amp;#34;
```&lt;/p&gt;
&lt;p&gt;It should be noted that by default `gatsby develop` is only accessible via the localhost `127.0.0.1`, and one would need to intentionally expose the server to other interfaces to exploit this vulnerability by using server options such as `--host 0.0.0.0`, `-H 0.0.0.0`, or the `GATSBY_HOST=0.0.0.0` environment variable.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;A patch has been introduced in `gatsby@5.9.1` and `gatsby@4.25.7` which mitigates the issue.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;As stated above, by default `gatsby develop` is only exposed to the localhost `127.0.0.1`.  For those using the develop server in the default configuration no risk is posed.  If other ranges are required, preventing the develop server from being exposed to untrusted interfaces or…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: gatsby&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;The Gatsby framework prior to versions 4.25.7 and 5.9.1 contain a Local File Inclusion vulnerability in the `__file-code-frame` and `__original-stack-frame` paths, exposed when running the Gatsby develop server (`gatsby develop`).&lt;/p&gt;
&lt;p&gt;The following steps can be used to reproduce the vulnerability:&lt;/p&gt;
&lt;p&gt;```
# Create a new Gatsby project
$ npm init gatsby
$ cd my-gatsby-site&lt;/p&gt;
&lt;p&gt;# Start the Gatsby develop server
$ gatsby develop&lt;/p&gt;
&lt;p&gt;# Execute the Local File Inclusion vulnerability in __file-code-frame
$ curl &amp;#34;http://127.0.0.1:8000/__file-code-frame?filePath=/etc/passwd&amp;amp;lineNumber=1&amp;#34;&lt;/p&gt;
&lt;p&gt;# Execute the Local File Inclusion vulnerability in __original-stack-frame
$ curl &amp;#34;http://127.0.0.1:8000/__original-stack-frame?moduleId=/etc/hosts&amp;amp;lineNumber=1&amp;amp;skipSourceMap=1&amp;#34;
```&lt;/p&gt;
&lt;p&gt;It should be noted that by default `gatsby develop` is only accessible via the localhost `127.0.0.1`, and one would need to intentionally expose the server to other interfaces to exploit this vulnerability by using server options such as `--host 0.0.0.0`, `-H 0.0.0.0`, or the `GATSBY_HOST=0.0.0.0` environment variable.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;A patch has been introduced in `gatsby@5.9.1` and `gatsby@4.25.7` which mitigates the issue.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;As stated above, by default `gatsby develop` is only exposed to the localhost `127.0.0.1`.  For those using the develop server in the default configuration no risk is posed.  If other ranges are required, preventing the develop server from being exposed to untrusted interfaces or…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-c6f8-8r25-c4gc</guid>
    </item>
    <item>
      <title>gsd-2023-34238</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2023-34238</link>
      <description>gsd-2023-34238</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2023-34238</guid>
    </item>
  </channel>
</rss>
