You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
🚨 [security] Update next 12.0.5 → 16.1.5 (major)#239
Closed
depfu[bot] wants to merge 1 commit intomainhttps-quantumblockchainai-atlassian-net/crystal-ai-nextjs-planetscale-starter:mainfrom
depfu/update/yarn/next-16.1.5https-quantumblockchainai-atlassian-net/crystal-ai-nextjs-planetscale-starter:depfu/update/yarn/next-16.1.5Copy head branch name to clipboard
depfu[bot] wants to merge 1 commit intomainhttps-quantumblockchainai-atlassian-net/crystal-ai-nextjs-planetscale-starter:mainfrom
depfu/update/yarn/next-16.1.5https-quantumblockchainai-atlassian-net/crystal-ai-nextjs-planetscale-starter:depfu/update/yarn/next-16.1.5Copy head branch name to clipboard
This is one of the first three pull requests with dependency updates we've sent your way. We tried to start with a few easy patch-level updates. Hopefully your tests will pass and you can merge this pull request without too much risk. This should give you an idea how Depfu works in general.
After you merge your first pull request, we'll send you a few more. We'll never open more than seven PRs at the same time so you're not getting overwhelmed with updates.
Let us know if you have any questions. Thanks so much for giving Depfu a try!
🚨 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.
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
@depfu rebase
Rebases against your default branch and redoes this update
@depfu recreate
Recreates this PR, overwriting any edits that you've made to it
@depfu merge
Merges this PR once your tests are passing and conflicts are resolved
@depfu cancel merge
Cancels automatic merging of this PR
@depfu close
Closes this PR and deletes the branch
@depfu reopen
Restores the branch and reopens this PR (if it's closed)
@depfu pause
Ignores all future updates for this dependency and closes this PR
@depfu pause [minor|major]
Ignores all future minor/major updates for this dependency and closes this PR
@depfu resume
Future versions of this dependency will create PRs again (leaves this PR as is)
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
Next steps: Take a moment to review the security alert
above. Review the linked package source code to understand the potential
risk. Ensure the package is not malicious before proceeding. If you're
unsure how to proceed, reach out to your security team or ask the Socket
team for help at support@socket.dev.
Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license.
Mark the package as acceptable risk. To ignore this alert only
in this pull request, reply with the comment
@SocketSecurity ignore npm/caniuse-lite@1.0.30001766. You can
also ignore all packages with @SocketSecurity ignore-all.
To ignore an alert for all future pull requests, use Socket's Dashboard to
change the triage state of this alert.
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
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.
Welcome to Depfu 👋
This is one of the first three pull requests with dependency updates we've sent your way. We tried to start with a few easy patch-level updates. Hopefully your tests will pass and you can merge this pull request without too much risk. This should give you an idea how Depfu works in general.
After you merge your first pull request, we'll send you a few more. We'll never open more than seven PRs at the same time so you're not getting overwhelmed with updates.
Let us know if you have any questions. Thanks so much for giving Depfu a try!
🚨 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 (12.0.5 → 16.1.5) · Repo
Security Advisories 🚨
🚨 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 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 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.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 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 Content Injection Vulnerability for Image Optimization
🚨 Next.JS vulnerability can lead to DoS via cache poisoning
🚨 Next.js has a Cache poisoning vulnerability due to omission of the Vary header
🚨 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
🚨 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
🚨 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 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
🚨 Next.js Cache Poisoning
🚨 Next.js Denial of Service (DoS) condition
🚨 Next.js Server-Side Request Forgery in Server Actions
🚨 Next.js Vulnerable to HTTP Request Smuggling
🚨 Next.js missing cache-control header may lead to CDN caching empty reply
🚨 Unexpected server crash in Next.js
🚨 Improper CSP in Image Optimization API for Next.js versions between 10.0.0 and 12.1.0
🚨 Denial of Service Vulnerability in next.js
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