fix: upgrade next to 16.2.11 (CVE-2026-64642) - #100
Open
anupamme wants to merge 3 commits into
Open
Conversation
Oliphaunt-History-Repair-Candidate: 3756e57
Automated dependency upgrade by OrbisAI Security
f0rr0
force-pushed
the
main
branch
3 times, most recently
from
July 28, 2026 09:25
8c75ffe to
a4f438c
Compare
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
2 participants
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 16.2.7 to 16.2.11 to fix CVE-2026-64642.
Vulnerability
CVE-2026-64642pnpm-lock.yamlDescription: Next.js: Middleware / Proxy bypass in App Router applications using Turbopack and single locale
Evidence
Scanner confirmation: trivy rule
CVE-2026-64642flagged 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
src/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