<?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://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-12T13:07:28.840988+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" 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://db.gcve.eu/vuln/fkie_cve-2026-119200</id>
    <title>fkie_cve-2026-119200</title>
    <updated>2026-11-12T13:07:28.842509+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Nuxt is an open-source web development framework for Vue.js. From 4.6.0 until 4.6.3, Nuxt resolves literal or percent-encoded dot segments before rendering a page while Nitro routing, server/middleware checks, and server route rules evaluate the unresolved path. A request such as /%2e/admin can therefore render app/pages/admin.vue and its server-rendered data while checks keyed to /admin, redirects, or per-route security headers do not apply. API handlers, appMiddleware, Nuxt 3, and Nuxt 4.0.0 through 4.5.x are not affected, and exploitation requires a client that sends dot segments without browser normalization. This issue is fixed in version 4.6.3.</p>
      </div>
    </content>
    <link href="https://db.gcve.eu/vuln/fkie_cve-2026-119200"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ghsa-9v7c-q64q-vv33</id>
    <title>GHSA-9v7c-q64q-vv33 — Nuxt: Dot segments in the request path bypass `server/middleware` path checks and server route rules on page routes</title>
    <updated>2026-11-12T13:07:28.842587+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: nuxt, npm: @nuxt/nitro-server</p>
<p>### Summary</p>
<p>Since `4.6.0`, Nuxt resolves `.` and `..` segments in the request path, including percent-encoded forms such as `%2e`, before rendering a page. Nitro's routing, Nitro's route rules and `server/middleware` see the path with those segments still in place. A request for `/%2e/admin` therefore renders the page at `/admin`, while server-side checks keyed on `/admin` do not apply.</p>
<p>### Impact</p>
<p>An unauthenticated attacker can bypass server-side controls that match on the request path of a page route.</p>
<p>`server/middleware` that checks `event.path` (or `event.node.req.url`) is skipped:</p>
<p>```ts
export default defineEventHandler((event) =&gt; {
  if (event.path.startsWith('/admin') &amp;&amp; !isAuthenticated(event)) {
    throw createError({ statusCode: 401 })
  }
})
```</p>
<p>With this middleware, `/admin` returns 401, but `/%2e/admin`, `/.%2e/admin` and `/x/%2e%2e/admin` reach the middleware with `event.path` set to `/./admin`, `/../admin` and `/x/../admin`, and render `app/pages/admin.vue` along with the data it fetches during server rendering.</p>
<p>Server-side `redirect` and `headers` route rules are skipped in the same way, so `'/admin/**': { redirect: '/login' }` does not redirect `/%2e/admin/secret`, and per-route security headers such as `Content-Security-Policy` are not sent.</p>
<p>Not affected:</p>
<p>- API handlers in `server/api` and `server/routes`. Nitro's router does not resolve dot segments, so these requests do not reach the handler.
- `appMiddleware` route rules and middleware declared…</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-9v7c-q64q-vv33"/>
  </entry>
</feed>
