@nuxt/nitro-server vulnerabilities
Nitro server integration for Nuxt
- Registry
- npm
- Latest
- 4.6.2
- License
- MIT
3 known advisories
The latest version, 4.6.2, is affected by 1 of them.
Security advisories for @nuxt/nitro-server
Nuxt: Server-side route rules (`redirect`, `headers`, `proxy`, `ssr`) are skipped for case-variant paths when routing is case-insensitive
- Affected
- >=4.2.0 <4.6.2 · >=3.20.0
- Fixed in
- 4.6.2
Nuxt's route middleware is not enforced when rendering `.server.vue` pages via `/__nuxt_island/page_*`
- Affected
- >=3.20.0 <3.21.6 · >=4.2.0 <4.4.6
- Fixed in
- 3.21.6, 4.4.6
Nuxt: `__nuxt_island` endpoint does not bind responses to request props, enabling shared-cache poisoning
- Affected
- >=3.20.0 <3.21.6 · >=4.2.0 <4.4.6
- Fixed in
- 3.21.6, 4.4.6
Which of your client projects still run an old @nuxt/nitro-server?
NPMscan reads the package-lock.json, yarn.lock and pnpm-lock.yaml in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other npm packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the npm registry.