@next/third-parties vulnerabilities (TuxCare)
32 vulnerabilities.
-
@next/third-partiesTuxCare Next.js: Information disclosure in Next.js App Router metadata image routes via dynamicParams bypass 6.3 Medium -
@next/third-partiesTuxCare Next.js: Server-Side Request Forgery in Image Optimization 8.3 High -
@next/third-partiesTuxCare Next.js: Information disclosure in the Next.js development server's Model Context Protocol endpoint 2.3 Low -
@next/third-partiesTuxCare Next.js: Middleware / Proxy bypass in App Router applications via segment-prefetch routes 7.5 High -
@next/third-partiesTuxCare Next.js: Middleware / Proxy bypass through dynamic route parameter injection 8.1 High -
@next/third-partiesTuxCare Next.js: Response Body Cache Confusion with Invalid UTF-8 Request Bodies 6.3 Medium -
@next/third-partiesTuxCare Next.js: Unbounded Server Action payload in Edge runtime 6.3 Medium -
@next/third-partiesTuxCare Next.js: Server-Side Request Forgery in rewrites via attacker-controlled destination hostname 8.3 High -
@next/third-partiesTuxCare Next.js: Unauthenticated Disclosure of Internal Server Function endpoints 6.3 Medium -
@next/third-partiesTuxCare Next.js: Cross-site scripting in App Router applications using CSP nonces 4.7 Medium -
@next/third-partiesTuxCare Next.js: Cross-site scripting in beforeInteractive scripts with untrusted input 6.1 Medium -
@next/third-partiesTuxCare Next.js: Denial of Service via connection exhaustion in applications using Cache Components 7.5 High -
@next/third-partiesTuxCare Next.js: Server-side request forgery in applications using WebSocket upgrades 8.6 High -
@next/third-partiesTuxCare Next.js: Denial of Service in the Image Optimization API 5.9 Medium -
@next/third-partiesTuxCare Next.js: Cache poisoning in React Server Component responses 5.4 Medium -
@next/third-partiesTuxCare Next.js HTTP request deserialization can lead to DoS when using insecure React Server Components 7.5 High -
@next/third-partiesTuxCare React Server Components have multiple Denial of Service Vulnerabilities 7.5 High -
@next/third-partiesTuxCare Next.js: Unbounded postponed resume buffering can lead to DoS 6.9 Medium -
@next/third-partiesTuxCare Next.js: null origin can bypass Server Actions CSRF checks 5.3 Medium -
@next/third-partiesTuxCare Next.js: null origin can bypass dev HMR websocket CSRF checks 2.3 Low -
@next/third-partiesTuxCare Next.js has Unbounded Memory Consumption via PPR Resume Endpoint 5.9 Medium -
@next/third-partiesTuxCare Next.js Vulnerable to Denial of Service with Server Components 5.9 Medium -
@next/third-partiesTuxCare Next.js: Cache poisoning of SSG and ISR pages in self-hosted Next.js applications 6.3 Medium -
@next/third-partiesTuxCare Next.js: Cache poisoning in Next.js SSG/ISR rendering leads to cross-user content substitution and persistent denial of service 6.3 Medium -
@next/third-partiesTuxCare Next.js: Unauthenticated Remote Code Execution on windows-hosted servers 9.0 Critical -
@next/third-partiesTuxCare Next.js: Response Body Cache Confusion for Requests Containing Bodies 6.0 Medium -
@next/third-partiesTuxCare Next.js: Denial of Service in App Router using Server Actions 8.2 High -
@next/third-partiesTuxCare Next.js: Cache poisoning via collisions in React Server Component cache-busting 3.7 Low -
@next/third-partiesTuxCare Denial of Service Vulnerability in React Server Components 7.5 High -
@next/third-partiesTuxCare Source Code Exposure Vulnerability in React Server Components 5.3 Medium -
@next/third-partiesTuxCare Next.js is vulnerable to RCE in React flight protocol 10.0 Critical -
@next/third-partiesTuxCare React Server Components are Vulnerable to RCE 10.0 Critical