Uh oh!
There was an error while loading. Please reload this page.
[Aikido] Fix security issue in next via minor version upgrade from 15.4.8 to 15.5.21 - #755
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 freeto 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 in WebSocket requests and multiple DoS vulnerabilities in App Router endpoints via malicious deserialization.
✅ 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 only stable, client-side Next.js features that remain unchanged in this version.
All breaking changes by upgrading next from version 15.4.8 to 15.5.21 (CHANGELOG)
experimental.strictNextHead: #81882window.next.turbopackinstead: #82580✅ 6 CVEs resolved by this upgrade
This PR will resolve the following CVEs:
🤖 Remediation details
Bump
nextto 15.5.21 to remediate multiple high/medium severity vulnerabilitiesShort summary
This PR remediates several high- and medium-severity vulnerabilities in the
nextpackage by upgrading it from15.4.8to15.5.21. The change is applied in two places: the rootpackage.json(devDependencies) and thepackages/demo-nextjs/package.jsonworkspace manifest, withyarn.lockrefreshed to reflect a single resolved instance at the new version.next
nextwas declared as an exact-pinned direct dependency in both the rootpackage.json(devDependencies) and thepackages/demo-nextjsworkspace manifest (dependencies), both at15.4.8. Both pins were updated to15.5.21— the minimum version that satisfies all advisories in scope, including CVE-2026-64644 which requires≥ 15.5.21(superseding the intermediate15.5.16floor set by the other advisories). After both manifest edits,yarn install --ignore-engines --ignore-scriptswas run from the lockfile root, collapsing the lockfile to a singlenext@15.5.21entry.Version changes
next15.4.815.5.21