<?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-05T20:27:22.772844+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-277276</id>
    <title>EUVD-2026-277276</title>
    <updated>2026-10-05T20:27:22.819774+00:00</updated>
    <content>EUVD-2026-277276</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-277276"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-33768</id>
    <title>fkie_cve-2026-33768</title>
    <updated>2026-10-05T20:27:22.819819+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Astro is a web framework. Prior to version 10.0.2, the @astrojs/vercel serverless entrypoint reads the x-astro-path header and x_astro_path query parameter to rewrite the internal request path, with no authentication whatsoever. On deployments without Edge Middleware, this lets anyone bypass Vercel's platform-level path restrictions entirely. The override preserves the original HTTP method and body, so this isn't limited to GET. POST, PUT, DELETE all land on the rewritten path. A Firewall rule blocking /admin/* does nothing when the request comes in as POST /api/health?x_astro_path=/admin/delete-user. This issue has been patched in version 10.0.2.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-33768"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-mr6q-rp88-fx84</id>
    <title>GHSA-mr6q-rp88-fx84 — Astro: Unauthenticated Path Override via `x-astro-path` / `x_astro_path`</title>
    <updated>2026-10-05T20:27:22.819858+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: @astrojs/vercel</p>
<p>## Summary</p>
<p>The `@astrojs/vercel` serverless entrypoint reads the `x-astro-path` header and `x_astro_path` query parameter to rewrite the internal request path, with no authentication whatsoever. On deployments without Edge Middleware, this lets anyone bypass Vercel's platform-level path restrictions entirely.</p>
<p>The override preserves the original HTTP method and body, so this isn't limited to GET. POST, PUT, DELETE all land on the rewritten path. A Firewall rule blocking `/admin/*` does nothing when the request comes in as `POST /api/health?x_astro_path=/admin/delete-user`.</p>
<p>## Affected Versions</p>
<p>Verified against:
- **Astro 5.18.1 + @astrojs/vercel 9.0.4** — GET and POST override both work. Full exploitation.
- **Astro 6.0.3 + @astrojs/vercel 10.0.0** — GET override works. POST/DELETE hit a `duplex` bug in the Request constructor (the `duplex: 'half'` option is required when passing a ReadableStream body — this has been an issue since Node.js 18 but is consistently enforced in the Node.js 22+ runtime that Astro 6 requires). This is not a security fix — the code explicitly passes `body: request.body` and intends to preserve it. Once the missing `duplex` option is added, all methods will be exploitable on v6 as well.</p>
<p>The vulnerable code path is identical across both versions.</p>
<p>## Affected Component</p>
<p>- **Package**: `@astrojs/vercel`
- **File**: `packages/integrations/vercel/src/serverless/entrypoint.ts` (lines 19–28)
- **Constants**: `packages/integrations/vercel/src/index.ts`…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-mr6q-rp88-fx84"/>
  </entry>
</feed>
