<?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-10T11:31:01.442082+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/bdu:2026-10656</id>
    <title>bdu:2026-10656</title>
    <updated>2026-10-10T11:31:01.444717+00:00</updated>
    <content>bdu:2026-10656</content>
    <link href="https://cve.radiocsirt.org/vuln/bdu:2026-10656"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-249356</id>
    <title>EUVD-2026-249356</title>
    <updated>2026-10-10T11:31:01.444748+00:00</updated>
    <content>EUVD-2026-249356</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-249356"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2025-54793</id>
    <title>fkie_cve-2025-54793</title>
    <updated>2026-10-10T11:31:01.444762+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 5.2.0 through 5.12.7, there is an Open Redirect vulnerability in the trailing slash redirection logic when handling paths with double slashes. This allows an attacker to redirect users to arbitrary external domains by crafting URLs such as https://mydomain.com//malicious-site.com/. This increases the risk of phishing and other social engineering attacks. This affects sites that use on-demand rendering (SSR) with the Node or Cloudflare adapters. It does not affect static sites, or sites deployed to Netlify or Vercel. This issue is fixed in version 5.12.8. To work around this issue at the network level, block outgoing redirect responses with a Location header value that starts with `//`.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2025-54793"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-cq8c-xv66-36gw</id>
    <title>GHSA-cq8c-xv66-36gw — Astros's duplicate trailing slash feature leads to an open redirection security issue</title>
    <updated>2026-10-10T11:31:01.444801+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: astro</p>
<p>## Summary</p>
<p>There is an Open Redirection vulnerability in the trailing slash redirection logic when handling paths with double slashes. This allows an attacker to redirect users to arbitrary external domains by crafting URLs such as `https://mydomain.com//malicious-site.com/`. This increases the risk of phishing and other social engineering attacks.</p>
<p>This affects Astro &gt;=5.2.0 sites that use on-demand rendering (SSR) with the Node or Cloudflare adapter. It does not affect static sites, or sites deployed to Netlify or Vercel.</p>
<p>## Background</p>
<p>Astro performs automatic redirection to the canonical URL, either adding or removing trailing slashes according to the value of the [`trailingSlash`](https://docs.astro.build/en/reference/configuration-reference/#trailingslash) configuration option. It follows the following rules:</p>
<p>- If `trailingSlash` is set to `"never"`, `https://example.com/page/` will redirect to `https://example.com/page` 
- If `trailingSlash` is set to `"always"`, `https://example.com/page` will redirect to `https://example.com/page/`</p>
<p>It also collapses multiple trailing slashes, according to the following rules:</p>
<p>- If `trailingSlash` is set to `"always"` or `"ignore"` (the default), `https://example.com/page//` will redirect to `https://example.com/page/`
- If `trailingSlash` is set to `"never"`, `https://example.com/page//` will redirect to `https://example.com/page`</p>
<p>It does this by returning a `301` redirect to the target path. The vulnerability occurs because…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-cq8c-xv66-36gw"/>
  </entry>
</feed>
