Update dependency next to v14.2.25 [SECURITY] #3
Conversation
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
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
|
🚨 gitStream Monthly Automation Limit Reached 🚨 Your organization has exceeded the number of pull requests allowed for automation with gitStream. To continue automating your PR workflows and unlock additional features, please contact LinearB. |
|
Important Review skippedBot user detected. To trigger a single review, invoke the You can disable this status message by setting the 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Join our Discord community for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
Reviewer's GuideUpgrades Next.js to v14.2.25 to apply a security patch for CVE-2025-29927, adjusting the project’s dependency declarations and lockfile to reflect the new version and updated package resolutions. Sequence Diagram: CVE-2025-29927 Authorization Bypass VulnerabilitysequenceDiagram
actor Attacker
participant NextApp as "Next.js App (<14.2.25)"
participant Middleware
Attacker->>+NextApp: HTTP Request with 'x-middleware-subrequest' header
NextApp->>+Middleware: Process request (vulnerable header handling)
Middleware-->>-NextApp: Authorization check bypassed
NextApp-->>-Attacker: Unauthorized Access / Data
Sequence Diagram: Patched Authorization Flow with Next.js 14.2.25sequenceDiagram
actor User
participant NextApp as "Next.js App (14.2.25+)"
participant Middleware
User->>+NextApp: HTTP Request (potentially with 'x-middleware-subrequest' header)
NextApp->>+Middleware: Process request (patched header handling)
Middleware->>-NextApp: Authorization check enforced
NextApp-->>-User: Appropriate Response (e.g., Access Denied if auth fails)
File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
CI Feedback 🧐A test triggered by this PR failed. Here is an AI-generated analysis of the failure:
|
renovate
bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
b970d68 to
639467e
Compare
renovate
bot
changed the title
|
🚨 gitStream Monthly Automation Limit Reached 🚨 Your organization has exceeded the number of pull requests allowed for automation with gitStream. To continue automating your PR workflows and unlock additional features, please contact LinearB. |
renovate
bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
639467e to
4468e07
Compare
renovate
bot
changed the title
|
🚨 gitStream Monthly Automation Limit Reached 🚨 Your organization has exceeded the number of pull requests allowed for automation with gitStream. To continue automating your PR workflows and unlock additional features, please contact LinearB. |
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.
This PR contains the following updates:
14.2.24->14.2.25GitHub Vulnerability Alerts
CVE-2025-29927
Impact
It is possible to bypass authorization checks within a Next.js application, if the authorization check occurs in middleware.
Patches
15.2.314.2.2513.5.912.3.5Note: 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-subrequestheader from reaching your Next.js application.Credits
Release Notes
vercel/next.js (next)
v14.2.25Compare Source
Core Changes
Credits
Huge thanks to @ijjk for helping!
Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.