<?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>Sat, 03 Oct 2026 13:29:13 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-242064</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-242064</link>
      <description>EUVD-2026-242064</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-242064</guid>
    </item>
    <item>
      <title>fkie_cve-2024-23340</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-23340</link>
      <description>&lt;p&gt;@hono/node-server is an adapter that allows users to run Hono applications on Node.js. Since v1.3.0, @hono/node-server has used its own Request object with `url` behavior that is unexpected. In the standard API, if the URL contains `..`, here called &amp;#34;double dots&amp;#34;, the URL string returned by Request will be in the resolved path. However, the `url` in @hono/node-server&amp;#39;s Request as does not resolve double dots, so `http://localhost/static/.. /foo.txt` is returned. This causes vulnerabilities when using `serveStatic`. Modern web browsers and a latest `curl` command resolve double dots on the client side, so this issue doesn&amp;#39;t affect those using either of those tools. However, problems may occur if accessed by a client that does not resolve them. Version 1.4.1 includes the change to fix this issue. As a workaround, don&amp;#39;t use `serveStatic`.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;@hono/node-server is an adapter that allows users to run Hono applications on Node.js. Since v1.3.0, @hono/node-server has used its own Request object with `url` behavior that is unexpected. In the standard API, if the URL contains `..`, here called &amp;#34;double dots&amp;#34;, the URL string returned by Request will be in the resolved path. However, the `url` in @hono/node-server&amp;#39;s Request as does not resolve double dots, so `http://localhost/static/.. /foo.txt` is returned. This causes vulnerabilities when using `serveStatic`. Modern web browsers and a latest `curl` command resolve double dots on the client side, so this issue doesn&amp;#39;t affect those using either of those tools. However, problems may occur if accessed by a client that does not resolve them. Version 1.4.1 includes the change to fix this issue. As a workaround, don&amp;#39;t use `serveStatic`.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-23340</guid>
    </item>
    <item>
      <title>GHSA-rjq5-w47x-x359 — @hono/node-server cannot handle "double dots" in URL</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-rjq5-w47x-x359</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: @hono/node-server&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;Since v1.3.0, we use our own Request object. This is great, but the `url` behavior is unexpected.&lt;/p&gt;
&lt;p&gt;In the standard API, if the URL contains `..`, here called &amp;#34;double dots&amp;#34;, the URL string returned by Request will be in the resolved path.&lt;/p&gt;
&lt;p&gt;```ts
const req = new Request(&amp;#39;http://localhost/static/../foo.txt&amp;#39;) // Web-standards
console.log(req.url) // http://localhost/foo.txt
```&lt;/p&gt;
&lt;p&gt;However, the `url` in our Request does not resolve double dots, so `http://localhost/static/.. /foo.txt` is returned.&lt;/p&gt;
&lt;p&gt;```ts
const req = new Request(&amp;#39;http://localhost/static/../foo.txt&amp;#39;)
console.log(req.url) // http://localhost/static/../foo.txt
```&lt;/p&gt;
&lt;p&gt;It will pass unresolved paths to the web application. This causes vulnerabilities like #123 when using `serveStatic`.&lt;/p&gt;
&lt;p&gt;Note: Modern web browsers and a latest `curl` command resolve double dots on the client side, so it does not affect you if the user uses them. However, problems may occur if accessed by a client that does not resolve them.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;&amp;#34;v1.4.1&amp;#34; includes the change to fix this issue.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;Don&amp;#39;t use `serveStatic`.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: @hono/node-server&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;Since v1.3.0, we use our own Request object. This is great, but the `url` behavior is unexpected.&lt;/p&gt;
&lt;p&gt;In the standard API, if the URL contains `..`, here called &amp;#34;double dots&amp;#34;, the URL string returned by Request will be in the resolved path.&lt;/p&gt;
&lt;p&gt;```ts
const req = new Request(&amp;#39;http://localhost/static/../foo.txt&amp;#39;) // Web-standards
console.log(req.url) // http://localhost/foo.txt
```&lt;/p&gt;
&lt;p&gt;However, the `url` in our Request does not resolve double dots, so `http://localhost/static/.. /foo.txt` is returned.&lt;/p&gt;
&lt;p&gt;```ts
const req = new Request(&amp;#39;http://localhost/static/../foo.txt&amp;#39;)
console.log(req.url) // http://localhost/static/../foo.txt
```&lt;/p&gt;
&lt;p&gt;It will pass unresolved paths to the web application. This causes vulnerabilities like #123 when using `serveStatic`.&lt;/p&gt;
&lt;p&gt;Note: Modern web browsers and a latest `curl` command resolve double dots on the client side, so it does not affect you if the user uses them. However, problems may occur if accessed by a client that does not resolve them.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;&amp;#34;v1.4.1&amp;#34; includes the change to fix this issue.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;Don&amp;#39;t use `serveStatic`.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-rjq5-w47x-x359</guid>
    </item>
    <item>
      <title>gsd-2024-23340</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2024-23340</link>
      <description>gsd-2024-23340</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2024-23340</guid>
    </item>
  </channel>
</rss>
