Repository navigation
Update npm package next to v15.5.27 [SECURITY] - #10016
hash-dependencies[bot] wants to merge 1 commit into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
3 Skipped Deployments
|
PR SummaryLow Risk Overview This is a patch-level framework upgrade to pick up Next.js security fixes (including SSG/ISR cache-poisoning and related advisories noted in the PR). No application source changes—only manifest and lockfile versions. Reviewed by Cursor Bugbot for commit 50027a1. Bugbot is set up for automated code reviews on this repo. Configure here. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #10016 +/- ##
==========================================
- Coverage 67.98% 67.98% -0.01%
==========================================
Files 1945 1946 +1
Lines 201674 201768 +94
Branches 8286 8314 +28
==========================================
+ Hits 137105 137164 +59
- Misses 62950 62979 +29
- Partials 1619 1625 +6
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
This PR contains the following updates:
15.5.25→15.5.27Next.js has cache poisoning in SSG/ISR rendering that leads to cross-user content substitution and persistent denial of service
CVE-2026-94484 / GHSA-mcj8-r9mp-w47p
More information
Details
Next.js applications that use a root-level catch-all page together with statically generated or Incremental Static Regeneration routes can have their shared response cache poisoned by a single unauthenticated crafted request.
Severity
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Next.js has cache poisoning of SSG and ISR pages in self-hosted applications
CVE-2026-94543 / GHSA-4jqv-mc3x-m676
More information
Details
Self-hosted Next.js applications that use the Pages Router with statically generated (SSG) or incrementally regenerated (ISR) pages can have a page's cache entry replaced with content from a different route, causing the affected page to serve wrong content to every visitor until the entry is revalidated. Applications deployed on Vercel are not affected.
Severity
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Release Notes
vercel/next.js (next)
v15.5.27Compare Source
This release contains security fixes for the following advisories:
Medium:
v15.5.26Compare Source
This release contains additional security hardening for
next/og. For more information, check out https://nextjs.org/blog/nextjs-security-update-september-22-2026Configuration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR has been generated by Mend Renovate CLI.