Skip to content
This repository was archived by the owner on Dec 11, 2025. It is now read-only.

🚨 [security] [js] Update all of nextjs 15.1.3 → 15.3.2 (minor)#2220

Closed
depfu[bot] wants to merge 1 commit intomasterfrom
depfu/update/npm/group/nextjs-15.3.2
Closed

🚨 [security] [js] Update all of nextjs 15.1.3 → 15.3.2 (minor)#2220
depfu[bot] wants to merge 1 commit intomasterfrom
depfu/update/npm/group/nextjs-15.3.2

Conversation

@depfu
Copy link
Contributor

@depfu depfu bot commented May 28, 2025


🚨 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?

✳️ @​next/eslint-plugin-next (15.1.3 → 15.3.2)

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

✳️ eslint-config-next (15.1.3 → 15.3.2)

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

✳️ next (15.1.3 → 15.3.2) · Repo

Security Advisories 🚨

🚨 Information exposure in Next.js dev server due to lack of origin verification

Summary

This vulnerability is similar to CVE-2018-14732. When running a Next.js server locally (e.g. through npm run dev), the WebSocket server is vulnerable to the Cross-site WebSocket hijacking (CSWSH) attack. and a bad actor can access the source code of client components, if a user was to visit a malicious link while having the Next.js dev server running.

Impact

If a user is running a Next.js server locally (e.g. npm run dev), and they were to browse to a malicious website, the malicious website may be able to access the source code of the Next.js app. This vulnerability only affects applications making use of App Router.

Note: App Router was experimental requiring experimental.appDir = true in versions >=13.0.0 to <13.4.

🚨 Next.js Race Condition to Cache Poisoning

Summary
We received a responsible disclosure from Allam Rachid (zhero) for a low-severity race-condition vulnerability in Next.js. This issue only affects the Pages Router under certain misconfigurations, causing normal endpoints to serve pageProps data instead of standard HTML.

Learn more here

Credit
Thank you to Allam Rachid (zhero) for the responsible disclosure. This research was rewarded as part of our bug bounty program.

🚨 Next.js may leak x-middleware-subrequest-id to external hosts

Summary

In the process of remediating CVE-2025-29927, we looked at other possible exploits of Middleware. We independently verified this low severity vulnerability in parallel with two reports from independent researchers.

Learn more here.

Credit

Thank you to Jinseo Kim kjsman and RyotaK (GMO Flatt Security Inc.) with takumi-san.ai for the responsible disclosure. These researchers were awarded as part of our bug bounty program.

🚨 Authorization Bypass in Next.js Middleware

Impact

It is possible to bypass authorization checks within a Next.js application, if the authorization check occurs in middleware.

Patches

  • For Next.js 15.x, this issue is fixed in 15.2.3
  • For Next.js 14.x, this issue is fixed in 14.2.25
  • For Next.js 13.x, this issue is fixed in 13.5.9
  • For Next.js 12.x, this issue is fixed in 12.3.5
  • For Next.js 11.x, consult the below workaround.

Note: Next.js deployments hosted on Vercel are automatically protected against this vulnerability.

Workaround

If patching to a safe version is infeasible, it is recommend that you prevent external user requests which contain the x-middleware-subrequest header from reaching your Next.js application.

Credits

  • Allam Rachid (zhero;)
  • Allam Yasser (inzo_)
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 7 commits:

✳️ semver (7.6.3 → 7.7.2) · Repo · Changelog

Release Notes

7.7.2

7.7.2 (2025-05-12)

Bug Fixes

Chores

7.7.1

7.7.1 (2025-02-03)

Bug Fixes

7.7.0

7.7.0 (2025-01-29)

Features

Bug Fixes

Documentation

Chores

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

Commits

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

↗️ @​emnapi/runtime (indirect, 1.3.1 → 1.4.3) · Repo

Release Notes

1.4.3

What's Changed

  • update @emnapi/wasi-threads@1.0.2 in the package.json dependency of @emnapi/core

Full Changelog: v1.4.2...v1.4.3

1.4.2

What's Changed

Full Changelog: v1.4.1...v1.4.2

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

Commits

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

↗️ @​img/sharp-darwin-arm64 (indirect, 0.33.5 → 0.34.2) · Repo

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ @​img/sharp-darwin-x64 (indirect, 0.33.5 → 0.34.2) · Repo

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ @​img/sharp-libvips-darwin-arm64 (indirect, 1.0.4 → 1.1.0) · Repo

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

↗️ @​img/sharp-libvips-darwin-x64 (indirect, 1.0.4 → 1.1.0) · Repo

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

↗️ @​img/sharp-libvips-linux-arm (indirect, 1.0.5 → 1.1.0) · Repo

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

↗️ @​img/sharp-libvips-linux-arm64 (indirect, 1.0.4 → 1.1.0) · Repo

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

↗️ @​img/sharp-libvips-linux-s390x (indirect, 1.0.4 → 1.1.0) · Repo

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

↗️ @​img/sharp-libvips-linux-x64 (indirect, 1.0.4 → 1.1.0) · Repo

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

↗️ @​img/sharp-libvips-linuxmusl-arm64 (indirect, 1.0.4 → 1.1.0) · Repo

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

↗️ @​img/sharp-libvips-linuxmusl-x64 (indirect, 1.0.4 → 1.1.0) · Repo

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

↗️ @​img/sharp-linux-arm (indirect, 0.33.5 → 0.34.2) · Repo

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ @​img/sharp-linux-arm64 (indirect, 0.33.5 → 0.34.2) · Repo

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ @​img/sharp-linux-s390x (indirect, 0.33.5 → 0.34.2) · Repo

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ @​img/sharp-linux-x64 (indirect, 0.33.5 → 0.34.2) · Repo

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ @​img/sharp-linuxmusl-arm64 (indirect, 0.33.5 → 0.34.2) · Repo

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ @​img/sharp-linuxmusl-x64 (indirect, 0.33.5 → 0.34.2) · Repo

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ @​img/sharp-wasm32 (indirect, 0.33.5 → 0.34.2) · Repo

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ @​img/sharp-win32-ia32 (indirect, 0.33.5 → 0.34.2) · Repo

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ @​img/sharp-win32-x64 (indirect, 0.33.5 → 0.34.2) · Repo

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ @​next/env (indirect, 15.1.3 → 15.3.2) · Repo

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 7 commits:

↗️ sharp (indirect, 0.33.5 → 0.34.2) · Repo

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

🆕 @​img/sharp-libvips-linux-ppc64 (added, 1.1.0)

🆕 @​img/sharp-win32-arm64 (added, 0.34.2)


Depfu Status

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 depfu bot added the depfu label May 28, 2025
@depfu depfu bot assigned effigies May 28, 2025
@codecov
Copy link

codecov bot commented May 28, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 85.70%. Comparing base (1ea4a93) to head (0956dde).

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #2220   +/-   ##
=======================================
  Coverage   85.70%   85.70%           
=======================================
  Files          91       91           
  Lines        3784     3784           
  Branches     1221     1221           
=======================================
  Hits         3243     3243           
  Misses        455      455           
  Partials       86       86           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@effigies effigies closed this Jun 17, 2025
@depfu depfu bot deleted the depfu/update/npm/group/nextjs-15.3.2 branch June 17, 2025 16:55
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant