<?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>Wed, 07 Oct 2026 19:52:04 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-341988</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-341988</link>
      <description>EUVD-2026-341988</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-341988</guid>
    </item>
    <item>
      <title>fkie_cve-2026-59730</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-59730</link>
      <description>&lt;p&gt;Astro is a web framework for content-driven websites. In versions 8.1.0 through 11.0.1, when trailingSlash: &amp;#39;always&amp;#39; is configured, the @astrojs/node standalone server&amp;#39;s static file handler appends a trailing slash to request paths and issues a 301 redirect. Paths beginning with /\ (slash-backslash) were not recognized as internal paths, so the handler would echo the raw path back in the Location header. Because browsers treat \ as / per the WHATWG URL specification, the resulting redirect could resolve to an external host. Preconditions for exploitation: trailingSlash: &amp;#39;always&amp;#39; must be set (non-default; the default is &amp;#39;ignore&amp;#39;), the request path must not have a file extension in its final segment, and an attacker must deliver the crafted link to a user. This issue has been fixed in version 11.0.2.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Astro is a web framework for content-driven websites. In versions 8.1.0 through 11.0.1, when trailingSlash: &amp;#39;always&amp;#39; is configured, the @astrojs/node standalone server&amp;#39;s static file handler appends a trailing slash to request paths and issues a 301 redirect. Paths beginning with /\ (slash-backslash) were not recognized as internal paths, so the handler would echo the raw path back in the Location header. Because browsers treat \ as / per the WHATWG URL specification, the resulting redirect could resolve to an external host. Preconditions for exploitation: trailingSlash: &amp;#39;always&amp;#39; must be set (non-default; the default is &amp;#39;ignore&amp;#39;), the request path must not have a file extension in its final segment, and an attacker must deliver the crafted link to a user. This issue has been fixed in version 11.0.2.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-59730</guid>
    </item>
    <item>
      <title>GHSA-r557-wffq-wvrc — @astrojs/node: Backslash-prefixed paths not recognized as internal by trailing-slash redirect</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-r557-wffq-wvrc</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: @astrojs/node&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;With `trailingSlash: &amp;#39;always&amp;#39;` configured, the `@astrojs/node` standalone server&amp;#39;s static file handler appends a trailing slash to request paths and issues a `301` redirect. Paths beginning with `/\` (slash-backslash) were not recognized as internal paths, so the handler would echo the raw path back in the `Location` header. Because browsers treat `\` as `/` per the WHATWG URL specification, the resulting redirect could resolve to an external host.&lt;/p&gt;
&lt;p&gt;**Preconditions:**
- `trailingSlash: &amp;#39;always&amp;#39;` must be set (non-default; the default is `&amp;#39;ignore&amp;#39;`)
- The request path must not have a file extension in its final segment
- An attacker must deliver the crafted link to a user&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;Fixed by treating backslash-prefixed paths the same as `//`-prefixed paths in `isInternalPath()`, so they are no longer rewritten with a trailing slash.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;Use the default `trailingSlash: &amp;#39;ignore&amp;#39;` setting, which does not issue trailing-slash redirects in the static file handler.&lt;/p&gt;
&lt;p&gt;### References&lt;/p&gt;
&lt;p&gt;- [WHATWG URL spec: backslash normalization](https://url.spec.whatwg.org/#url-parsing)&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: @astrojs/node&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;With `trailingSlash: &amp;#39;always&amp;#39;` configured, the `@astrojs/node` standalone server&amp;#39;s static file handler appends a trailing slash to request paths and issues a `301` redirect. Paths beginning with `/\` (slash-backslash) were not recognized as internal paths, so the handler would echo the raw path back in the `Location` header. Because browsers treat `\` as `/` per the WHATWG URL specification, the resulting redirect could resolve to an external host.&lt;/p&gt;
&lt;p&gt;**Preconditions:**
- `trailingSlash: &amp;#39;always&amp;#39;` must be set (non-default; the default is `&amp;#39;ignore&amp;#39;`)
- The request path must not have a file extension in its final segment
- An attacker must deliver the crafted link to a user&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;Fixed by treating backslash-prefixed paths the same as `//`-prefixed paths in `isInternalPath()`, so they are no longer rewritten with a trailing slash.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;Use the default `trailingSlash: &amp;#39;ignore&amp;#39;` setting, which does not issue trailing-slash redirects in the static file handler.&lt;/p&gt;
&lt;p&gt;### References&lt;/p&gt;
&lt;p&gt;- [WHATWG URL spec: backslash normalization](https://url.spec.whatwg.org/#url-parsing)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-r557-wffq-wvrc</guid>
    </item>
  </channel>
</rss>
