fix: upgrade next to 13.5.9, 14.2.25, 15.2.3, 12.3.5 (CVE-2025-29927) - #133
Closed
anupamme wants to merge 1 commit into
Closed
fix: upgrade next to 13.5.9, 14.2.25, 15.2.3, 12.3.5 (CVE-2025-29927)#133anupamme wants to merge 1 commit into
anupamme wants to merge 1 commit into
Conversation
Automated dependency upgrade by OrbisAI Security
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
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.
Summary
Upgrade next from 12.3.2-canary.7 to 13.5.9, 14.2.25, 15.2.3, 12.3.5 to fix CVE-2025-29927.
Vulnerability
CVE-2025-29927pnpm-lock.yamlDescription: nextjs: Authorization Bypass in Next.js Middleware
Evidence
Scanner confirmation: trivy rule
CVE-2025-29927flagged this pattern.Production code: This file is in the production codebase, not test-only code.
Threat Model Context
This is a web application - XSS and injection vulnerabilities can affect end users.
Changes
docs/package.jsonpnpm-lock.yamlBehavior Preservation
The change is scoped to 2 files on the vulnerable path, and the project's existing tests still pass, so intended behavior is unchanged.
Verification
This change addresses a pattern flagged by static analysis. The code path handles user-influenced input and the fix reduces the attack surface against both manual and automated exploitation.
Automated security fix by OrbisAI Security