Repository navigation
🚨 [security] Update next 14.2.1 → 16.4.2 (major) - #99
Open
depfu[bot] wants to merge 1 commit into
Open
depfu[bot] wants to merge 1 commit into
depfu[bot] wants to merge 1 commit into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch had an error being deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🚨 Your current dependencies have known security vulnerabilities 🚨
This dependency update fixes known security vulnerabilities. Please see the details below and assess their impact carefully. We recommend to merge and deploy this as soon as possible!
Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ next (14.2.1 → 16.4.2) · Repo
Security Advisories 🚨
🚨 Next.js: Denial of Service in App Router using Server Actions
🚨 Next.js: Denial of Service in App Router using Server Actions
🚨 Next.js: Unauthenticated Remote Code Execution in Image Optimization API when SVG files are used
🚨 Next.js: Unauthenticated Remote Code Execution in Image Optimization API when SVG files are used
🚨 Next.js has cache poisoning in SSG/ISR rendering that leads to cross-user content substitution and persistent denial of service
🚨 Next.js has cache poisoning of SSG and ISR pages in self-hosted applications
🚨 Next.js has information disclosure in App Router metadata image routes via dynamicParams bypass
🚨 Next.js has cache poisoning in SSG/ISR rendering that leads to cross-user content substitution and persistent denial of service
🚨 Next.js has information disclosure in development server's Model Context Protocol endpoint
🚨 Next.js has cache poisoning of SSG and ISR pages in self-hosted applications
🚨 Next.js has Server-Side Request Forgery in Image Optimization
🚨 Next.js: Pending `use cache` fill can leak Draft Mode content into regular responses and persisted pages
🚨 Next.js: Remote Code Execution in next/og ImageResponse
🚨 Next.js: Unauthenticated Remote Code Execution on windows-hosted servers
🚨 Next.js: Unauthenticated Remote Code Execution on windows-hosted servers
🚨 Next.js: Unauthenticated Remote Code Execution in Image Optimization API when AVIF files are used
🚨 Next.js: Unauthenticated Remote Code Execution in Image Optimization API when AVIF files are used
🚨 Next.js: Server-Side Request Forgery in rewrites via attacker-controlled destination hostname
🚨 Next.js: Middleware / Proxy bypass in App Router applications using Turbopack and single locale
🚨 Next.js: Server-Side Request Forgery in Server Actions on custom servers
🚨 Next.js: Cache confusion of response bodies for requests with bodies containing invalid UTF-8 byte sequences
🚨 Next.js: Unbounded Server Action payload in Edge runtime
🚨 Next.js: Denial of Service in the Image Optimization API using SVGs
🚨 Next.js: Unauthenticated disclosure of internal Server Function endpoints
🚨 Next.js: Denial of Service in App Router using Server Actions
🚨 Next.js: Server-Side Request Forgery in Server Actions on custom servers
🚨 Next.js: Unbounded Server Action payload in Edge runtime
🚨 Next.js: Unauthenticated disclosure of internal Server Function endpoints
🚨 Next.js: Server-Side Request Forgery in rewrites via attacker-controlled destination hostname
🚨 Next.js: Cache confusion of response bodies for requests with bodies
🚨 Next.js: Denial of Service in App Router using Server Actions
🚨 Next.js: Cache confusion of response bodies for requests with bodies containing invalid UTF-8 byte sequences
🚨 Next.js: Denial of Service in the Image Optimization API using SVGs
🚨 Next.js: Cache confusion of response bodies for requests with bodies
🚨 Next.js vulnerable to cache poisoning via collisions in React Server Component cache-busting
🚨 Next.js Vulnerable to Denial of Service with Server Components
🚨 Next.js has a Middleware / Proxy bypass in App Router applications via segment-prefetch routes
🚨 Next.js vulnerable to server-side request forgery in applications using WebSocket upgrades
🚨 Next.js has cross-site scripting in beforeInteractive scripts with untrusted input
🚨 Next.js Vulnerable to Denial of Service with Server Components
🚨 Next.js has a Middleware / Proxy bypass in Pages Router applications using i18n
🚨 Next.js has a Middleware / Proxy bypass in Pages Router applications using i18n
🚨 Next.js has a Middleware / Proxy bypass in App Router applications via segment-prefetch routes
🚨 Next.js vulnerable to cache poisoning in React Server Component responses
🚨 Next.js vulnerable to cache poisoning in React Server Component responses
🚨 Next.js has a Middleware / Proxy bypass through dynamic route parameter injection
🚨 Next.js has a Middleware / Proxy bypass through dynamic route parameter injection
🚨 Next.js vulnerable to server-side request forgery in applications using WebSocket upgrades
🚨 Next.js has a Denial of Service in the Image Optimization API
🚨 Next.js has a Denial of Service in the Image Optimization API
🚨 Next.js vulnerable to Denial of Service via connection exhaustion in applications using Cache Components
🚨 Next.js vulnerable to Denial of Service via connection exhaustion in applications using Cache Components
🚨 Next.js has cross-site scripting in beforeInteractive scripts with untrusted input
🚨 Next.js vulnerable to cache poisoning via collisions in React Server Component cache-busting
🚨 Next.js vulnerable to cross-site scripting in App Router applications using CSP nonces
🚨 Next.js vulnerable to cross-site scripting in App Router applications using CSP nonces
🚨 Next.js's Middleware / Proxy redirects can be cache-poisoned
🚨 Next.js's Middleware / Proxy redirects can be cache-poisoned
🚨 Next.js has a Middleware / Proxy bypass in App Router applications via segment-prefetch routes - Incomplete Fix Follow-Up
🚨 Next.js has a Middleware / Proxy bypass in App Router applications via segment-prefetch routes - Incomplete Fix Follow-Up
🚨 Next.js has a Denial of Service with Server Components
🚨 Next.js has a Denial of Service with Server Components
🚨 Next.js: Unbounded next/image disk cache growth can exhaust storage
🚨 Next.js: null origin can bypass dev HMR websocket CSRF checks
🚨 Next.js: null origin can bypass Server Actions CSRF checks
🚨 Next.js: Unbounded postponed resume buffering can lead to DoS
🚨 Next.js: Unbounded next/image disk cache growth can exhaust storage
🚨 Next.js: HTTP request smuggling in rewrites
🚨 Next.js: HTTP request smuggling in rewrites
🚨 Next.js has Unbounded Memory Consumption via PPR Resume Endpoint
🚨 Next.js has Unbounded Memory Consumption via PPR Resume Endpoint
🚨 Next.js HTTP request deserialization can lead to DoS when using insecure React Server Components
🚨 Next.js HTTP request deserialization can lead to DoS when using insecure React Server Components
🚨 Next.js HTTP request deserialization can lead to DoS when using insecure React Server Components
🚨 Next.js HTTP request deserialization can lead to DoS when using insecure React Server Components
🚨 Next.js HTTP request deserialization can lead to DoS when using insecure React Server Components
🚨 Next.js HTTP request deserialization can lead to DoS when using insecure React Server Components
🚨 Next.js HTTP request deserialization can lead to DoS when using insecure React Server Components
🚨 Next.js HTTP request deserialization can lead to DoS when using insecure React Server Components
🚨 Next.js HTTP request deserialization can lead to DoS when using insecure React Server Components
🚨 Next.js self-hosted applications vulnerable to DoS via Image Optimizer remotePatterns configuration
🚨 Next.js self-hosted applications vulnerable to DoS via Image Optimizer remotePatterns configuration
🚨 Next has a Denial of Service with Server Components - Incomplete Fix Follow-Up
🚨 Next has a Denial of Service with Server Components - Incomplete Fix Follow-Up
🚨 Next has a Denial of Service with Server Components - Incomplete Fix Follow-Up
🚨 Next has a Denial of Service with Server Components - Incomplete Fix Follow-Up
🚨 Next has a Denial of Service with Server Components - Incomplete Fix Follow-Up
🚨 Next has a Denial of Service with Server Components - Incomplete Fix Follow-Up
🚨 Next has a Denial of Service with Server Components - Incomplete Fix Follow-Up
🚨 Next has a Denial of Service with Server Components - Incomplete Fix Follow-Up
🚨 Next has a Denial of Service with Server Components - Incomplete Fix Follow-Up
🚨 Next Server Actions Source Code Exposure
🚨 Next Server Actions Source Code Exposure
🚨 Next Vulnerable to Denial of Service with Server Components
🚨 Next Vulnerable to Denial of Service with Server Components
🚨 Next Vulnerable to Denial of Service with Server Components
🚨 Next Vulnerable to Denial of Service with Server Components
🚨 Next Vulnerable to Denial of Service with Server Components
🚨 Next Vulnerable to Denial of Service with Server Components
🚨 Next Vulnerable to Denial of Service with Server Components
🚨 Next Vulnerable to Denial of Service with Server Components
🚨 Next Vulnerable to Denial of Service with Server Components
🚨 Next Server Actions Source Code Exposure
🚨 Next Server Actions Source Code Exposure
🚨 Next Server Actions Source Code Exposure
🚨 Next Server Actions Source Code Exposure
🚨 Next Server Actions Source Code Exposure
🚨 Next Server Actions Source Code Exposure
🚨 Next.js is vulnerable to RCE in React flight protocol
🚨 Next.js is vulnerable to RCE in React flight protocol
🚨 Next.js is vulnerable to RCE in React flight protocol
🚨 Next.js is vulnerable to RCE in React flight protocol
🚨 Next.js is vulnerable to RCE in React flight protocol
🚨 Next.js is vulnerable to RCE in React flight protocol
🚨 Next.js is vulnerable to RCE in React flight protocol
🚨 Next.js Affected by Cache Key Confusion for Image Optimization API Routes
🚨 Next.js Content Injection Vulnerability for Image Optimization
🚨 Next.js Improper Middleware Redirect Handling Leads to SSRF
🚨 Next.js Content Injection Vulnerability for Image Optimization
🚨 Next.js Improper Middleware Redirect Handling Leads to SSRF
🚨 Next.js has a Cache poisoning vulnerability due to omission of the Vary header
🚨 Next.JS vulnerability can lead to DoS via cache poisoning
🚨 Information exposure in Next.js dev server due to lack of origin verification
🚨 Information exposure in Next.js dev server due to lack of origin verification
🚨 Next.js Race Condition to Cache Poisoning
🚨 Next.js Race Condition to Cache Poisoning
🚨 Next.js may leak x-middleware-subrequest-id to external hosts
🚨 Next.js may leak x-middleware-subrequest-id to external hosts
🚨 Authorization Bypass in Next.js Middleware
🚨 Authorization Bypass in Next.js Middleware
🚨 Next.js Allows a Denial of Service (DoS) with Server Actions
🚨 Next.js Allows a Denial of Service (DoS) with Server Actions
🚨 Next.js authorization bypass vulnerability
🚨 Denial of Service condition in Next.js image optimization
🚨 Next.js Cache Poisoning
Release Notes
Too many releases to show here. View the full release notes.
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase.All Depfu comment commands