<?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://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-07T19:19:24.582147+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" 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://cve.radiocsirt.org/vuln/euvd-2026-341988</id>
    <title>EUVD-2026-341988</title>
    <updated>2026-10-07T19:19:24.641369+00:00</updated>
    <content>EUVD-2026-341988</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-341988"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-59730</id>
    <title>fkie_cve-2026-59730</title>
    <updated>2026-10-07T19:19:24.641413+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Astro is a web framework for content-driven websites. In versions 8.1.0 through 11.0.1, when trailingSlash: 'always' is configured, the @astrojs/node standalone server'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: 'always' must be set (non-default; the default is 'ignore'), 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.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-59730"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-r557-wffq-wvrc</id>
    <title>GHSA-r557-wffq-wvrc — @astrojs/node: Backslash-prefixed paths not recognized as internal by trailing-slash redirect</title>
    <updated>2026-10-07T19:19:24.641471+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: @astrojs/node</p>
<p>### Impact</p>
<p>With `trailingSlash: 'always'` configured, the `@astrojs/node` standalone server'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.</p>
<p>**Preconditions:**
- `trailingSlash: 'always'` must be set (non-default; the default is `'ignore'`)
- The request path must not have a file extension in its final segment
- An attacker must deliver the crafted link to a user</p>
<p>### Patches</p>
<p>Fixed by treating backslash-prefixed paths the same as `//`-prefixed paths in `isInternalPath()`, so they are no longer rewritten with a trailing slash.</p>
<p>### Workarounds</p>
<p>Use the default `trailingSlash: 'ignore'` setting, which does not issue trailing-slash redirects in the static file handler.</p>
<p>### References</p>
<p>- [WHATWG URL spec: backslash normalization](https://url.spec.whatwg.org/#url-parsing)</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-r557-wffq-wvrc"/>
  </entry>
</feed>
