🚨 [security] Update all of nextjs 16.1.6 → 16.1.7 (patch)#780
🚨 [security] Update all of nextjs 16.1.6 → 16.1.7 (patch)#780depfu[bot] wants to merge 4 commits intomainfrom
Conversation
Changed Files
|
👋 Hi there!Update the dependencies "next" from "16.1.6" to "16.1.7" and "eslint-config-next" from "^16.1.6" to "^16.1.7" in
|
Please double check the following review of the pull request:
Changes in the diff
Identified IssuesNo issues found in the incoming changes. SummaryThe pull request updates the Next.js package and its ESLint config to a newer patch version. This is a typical security or bugfix patch update. No code logic changes or new features are introduced. The update is straightforward and does not introduce any mistakes, typos, security issues, performance regressions, or readability problems. Missing testsNo tests are required for this dependency version bump. Summon me to re-review when updated! Yours, Gooroo.dev |
guibranco
left a comment
There was a problem hiding this comment.
Automatically approved by gstraccini[bot]
|
@depfu merge |
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
|
Caution Review the following alerts detected in dependencies. According to your organization's Security Policy, you must resolve all "Block" alerts before proceeding. Learn more about Socket for GitHub.
|
|
|
Infisical secrets check: ✅ No secrets leaked! Scan results: |
|
Closing because this update has already been applied |



🚨 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?
✳️ eslint-config-next (16.1.6 → 16.1.7)
Sorry, we couldn't find anything useful about this release.
✳️ next (16.1.6 → 16.1.7) · Repo
Security Advisories 🚨
🚨 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
Sorry, we couldn't find anything useful about this release.
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