[Aikido] Fix security issue in next via minor version upgrade from 15.4.8 to 15.5.21 - #754
Open
aikido-autofix[bot] wants to merge 1 commit into
Open
Conversation
|
🚨 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. |
✅ Security Analysis ResultsGreat news! No security issues found in this pull request. Analysis Summary:
💡 Trigger a new security scan by commenting Security analysis powered by Claude Sonnet 4.6 via pr-auditor | Questions? Contact #dx-team or check out this page |
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.
Upgrade Next.js to fix SSRF via WebSocket requests, DoS attacks on Server Functions, authorization bypass in middleware, and source code disclosure vulnerabilities.
✅ Code not affected by breaking changes.
✅ No breaking changes from the Next.js 15.4.8 → 15.5.16 upgrade affect this codebase. The demo application uses standard Next.js features (Pages Router, App Router,
useRouter,useSearchParams,Link) that remain unchanged. None of the deprecated or removed features (experimental.dynamicIO,useMDXComponents,experimental.strictNextHead,cookies()/headers()sync access, AMP,unstable_rootParams) are used in this codebase.All breaking changes by upgrading next from version 15.4.8 to 15.5.21 (CHANGELOG)
experimental.strictNextHead: #81882window.next.turbopackinstead: #82580✅ 5 CVEs resolved by this upgrade
This PR will resolve the following CVEs:
🤖 Remediation details
Upgrade
nextto resolve multiple security vulnerabilitiesShort summary
This PR fixes security vulnerabilities in the
nextpackage by upgrading it from15.4.8to15.5.21in both the rootpackage.json(devDependencies) and thepackages/demo-nextjsworkspace member manifest (dependencies). Theyarn.locklockfile was refreshed accordingly, replacing the old resolved entry with the single patched version.next
nextwas pinned at the exact version15.4.8in two places: the rootpackage.jsondevDependencies and thepackages/demo-nextjsworkspacepackage.jsondependencies. Both declarations were updated to the exact version15.5.21, which is the minimum release in the15.xline that satisfies all six advisories addressed by this task—including CVE-2026-64644, which required at least15.5.21and was introduced as a gap when an intermediate upgrade stopped at15.5.16. After both manifest edits,yarn install --ignore-engines --ignore-scriptswas run from the workspace root to produce a clean lockfile with a singlenext@15.5.21entry and no stale15.4.8or15.5.16residuals.Version changes
next15.4.815.5.21package.jsondevDependencies)next15.4.815.5.21packages/demo-nextjsdependencies)@next/env15.4.815.5.21next@next/swc-linux-x64-gnu15.4.815.5.21next@next/swc-linux-x64-musl15.4.815.5.21next