<?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>Tue, 06 Oct 2026 13:04:13 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-354998</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-354998</link>
      <description>EUVD-2026-354998</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-354998</guid>
    </item>
    <item>
      <title>fkie_cve-2026-73424</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-73424</link>
      <description>&lt;p&gt;Astro is a web framework for content-driven websites. From 10.0.3 until 11.0.3, the Astro Vercel adapter in packages/integrations/vercel/src/serverless/entrypoint.ts accepts x_astro_path for the public /_isr function based only on the x-vercel-isr header, allowing unauthenticated GET requests to render routes protected only by Vercel edge path rules or split edge middleware. This issue is fixed in 11.0.3.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Astro is a web framework for content-driven websites. From 10.0.3 until 11.0.3, the Astro Vercel adapter in packages/integrations/vercel/src/serverless/entrypoint.ts accepts x_astro_path for the public /_isr function based only on the x-vercel-isr header, allowing unauthenticated GET requests to render routes protected only by Vercel edge path rules or split edge middleware. This issue is fixed in 11.0.3.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-73424</guid>
    </item>
    <item>
      <title>GHSA-x27w-589x-frm2 — Astro: Unauthenticated path override in the @astrojs/vercel ISR function</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-x27w-589x-frm2</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: @astrojs/vercel&lt;/p&gt;
&lt;p&gt;## Summary
When ISR is enabled, the serverless entrypoint lets an unauthenticated request
decide which route the origin renders. The internal `_isr` function reads the
`x_astro_path` query parameter and rewrites the request path to it without any
authentication. Edge level access controls only ever see the `/_isr` path, so
they do not apply to the route that actually gets rendered. This is the same
confused deputy problem as CVE-2026-33768, reachable again through the ISR path.&lt;/p&gt;
&lt;p&gt;## Impact
This affects apps that use `@astrojs/vercel` with `isr: true` and protect routes
at the edge. Two common setups are affected:&lt;/p&gt;
&lt;p&gt;1. Path rules or firewall deny rules configured on Vercel (for example blocking
   `/admin`).
2. Split deployments (`edgeMiddleware: true`) where authorization lives in Astro
   middleware, since that middleware runs at the edge and not in the origin.&lt;/p&gt;
&lt;p&gt;An attacker reads any GET rendered route by requesting
`/_isr?x_astro_path=/the/protected/path`. No credentials are required. The
protected content is produced by a fresh origin render, so the attack does not
depend on the response being cached first.&lt;/p&gt;
&lt;p&gt;## Details
`packages/integrations/vercel/src/serverless/entrypoint.ts` picks the real path
like this:&lt;/p&gt;
&lt;p&gt;```js
if (hasValidMiddlewareSecret) {
  realPath = request.headers.get(ASTRO_PATH_HEADER);       // secret checked
} else if (request.headers.get(&amp;#39;x-vercel-isr&amp;#39;) === &amp;#39;1&amp;#39;) {
  realPath = url.searchParams.get(ASTRO_PATH_PARAM);        // no secret checked
}
```&lt;/p&gt;
&lt;p&gt;The head…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: @astrojs/vercel&lt;/p&gt;
&lt;p&gt;## Summary
When ISR is enabled, the serverless entrypoint lets an unauthenticated request
decide which route the origin renders. The internal `_isr` function reads the
`x_astro_path` query parameter and rewrites the request path to it without any
authentication. Edge level access controls only ever see the `/_isr` path, so
they do not apply to the route that actually gets rendered. This is the same
confused deputy problem as CVE-2026-33768, reachable again through the ISR path.&lt;/p&gt;
&lt;p&gt;## Impact
This affects apps that use `@astrojs/vercel` with `isr: true` and protect routes
at the edge. Two common setups are affected:&lt;/p&gt;
&lt;p&gt;1. Path rules or firewall deny rules configured on Vercel (for example blocking
   `/admin`).
2. Split deployments (`edgeMiddleware: true`) where authorization lives in Astro
   middleware, since that middleware runs at the edge and not in the origin.&lt;/p&gt;
&lt;p&gt;An attacker reads any GET rendered route by requesting
`/_isr?x_astro_path=/the/protected/path`. No credentials are required. The
protected content is produced by a fresh origin render, so the attack does not
depend on the response being cached first.&lt;/p&gt;
&lt;p&gt;## Details
`packages/integrations/vercel/src/serverless/entrypoint.ts` picks the real path
like this:&lt;/p&gt;
&lt;p&gt;```js
if (hasValidMiddlewareSecret) {
  realPath = request.headers.get(ASTRO_PATH_HEADER);       // secret checked
} else if (request.headers.get(&amp;#39;x-vercel-isr&amp;#39;) === &amp;#39;1&amp;#39;) {
  realPath = url.searchParams.get(ASTRO_PATH_PARAM);        // no secret checked
}
```&lt;/p&gt;
&lt;p&gt;The head…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-x27w-589x-frm2</guid>
    </item>
  </channel>
</rss>
