🚨 [security] Update all of nextjs 15.4.4 → 15.4.7 (patch)

[depfu]

---

🚨 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 update. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ eslint-config-next (15.4.4 → 15.4.7)

Sorry, we couldn't find anything useful about this release.

✳️ next (15.4.4 → 15.4.7) · Repo

Security Advisories 🚨

🚨 Next.js Content Injection Vulnerability for Image Optimization

A vulnerability in Next.js Image Optimization has been fixed in v15.4.5 and v14.2.31. The issue allowed attacker-controlled external image sources to trigger file downloads with arbitrary content and filenames under specific configurations. This behavior could be abused for phishing or malicious file delivery.

All users relying on images.domains or images.remotePatterns are encouraged to upgrade and verify that external image sources are strictly validated.

More details at Vercel Changelog

🚨 Next.js Affected by Cache Key Confusion for Image Optimization API Routes

A vulnerability in Next.js Image Optimization has been fixed in v15.4.5 and v14.2.31. When images returned from API routes vary based on request headers (such as Cookie or Authorization), these responses could be incorrectly cached and served to unauthorized users due to a cache key confusion bug.

All users are encouraged to upgrade if they use API routes to serve images that depend on request headers and have image optimization enabled.

More details at Vercel Changelog

🚨 Next.js Improper Middleware Redirect Handling Leads to SSRF

A vulnerability in Next.js Middleware has been fixed in v14.2.32 and v15.4.7. The issue occurred when request headers were directly passed into NextResponse.next(). In self-hosted applications, this could allow Server-Side Request Forgery (SSRF) if certain sensitive headers from the incoming request were reflected back into the response.

All users implementing custom middleware logic in self-hosted environments are strongly encouraged to upgrade and verify correct usage of the next() function.

More details at Vercel Changelog

Release Notes

15.4.7

Note

This release is backporting bug fixes. It does not include all pending features/changes on canary.

Core Changes

• fix router handling when setting a location response header #82588

Credits

Huge thanks to @ztanner for helping!

15.4.6

Note

This release is backporting bug fixes. It does not include all pending features/changes on canary.

Core Changes

• fix: _error page's req.url can be overwritten to dynamic param on minimal mode (#82347)
• fix: add ?dpl to fonts in /_next/static/media (#82384)

Credits

Huge thanks to @devjiwonchoi, @ijjk, and @styfle for helping!

15.4.5

Note

This release is backporting bug fixes. It does not include all pending features/changes on canary.

Core Changes

• Fix API stripping JSON incorrectly (#82062)
• Fix i18n fallback: false collision (#82158)
• Revert "Fix tracing of server actions imported by client components (#82167)
• Ensure setAssetPrefix updates config instance (#82165)
• Turbopack: update mimalloc (#82166)
• fix(next/image): fix image-optimizer.ts headers (#82175)
• fix(next/image): improve and simplify detect-content-type (#82174)

Credits

Huge thanks to @ijjk, @sokra, and @styfle for helping!

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 14 commits:

• v15.4.7
• fix router handling when setting a location response header (#82588)
• v15.4.6
• Backport "fix: add `?dpl` to fonts in `/_next/static/media` (#82384)" (#82421)
• Backport "[Pages] fix: `_error` page's `req.url` can be overwritten t… (#82377)
• v15.4.5
• Disable test new tests jobs
• [backport]: fix(next/image): improve and simplify detect-content-type (#82118) (#82174)
• [backport]: fix(next/image): fix image-optimizer.ts headers (#82114) (#82175)
• Backport: Turbopack: update mimalloc (#81993) (#82166)
• [backport] Ensure setAssetPrefix updates config instance (#82165)
• [Backport] Revert "Fix tracing of server actions imported by client components (#78968) (#82167)
• [backport] Fix i18n fallback: false collision (#82158)
• Fix API stripping JSON incorrectly (#82062)

---

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)

[depfu]

Sorry, but the merge failed with:

At least 1 approving review is required by reviewers with write access.