Bump next from 15.5.12 to 15.5.15

[dependabot]

Bumps next from 15.5.12 to 15.5.15.

Release notes

Sourced from next's releases.

v15.5.15

Please refer the following changelogs for more information about this security release:

https://vercel.com/changelog/summary-of-cve-2026-23869

v15.5.14

[!NOTE] This release is backporting bug fixes. It does not include all pending features/changes on canary.

Core Changes

• feat(next/image): add lru disk cache and images.maximumDiskCacheSize (#91660)
• Fix(pages-router): restore Content-Length and ETag for /_next/data/ JSON responses (#90304)

Credits

Huge thanks to @​styfle and @​lllomh for helping!

v15.5.13

[!NOTE] This release is backporting bug fixes. It does not include all pending features/changes on canary.

Core Changes

• fix: patch http-proxy to prevent request smuggling in rewrites (See: CVE-2026-29057)

Credits

Huge thanks to @​ztanner for helping!

Commits

• 412eb90 v15.5.15
• cb90de9 [15.x] Avoid consuming cyclic models multiple times (#74)
• fffef9e Fix CI for glibc linux builds
• d7b012d v15.5.14
• 2b05251 [backport] feat(next/image): add lru disk cache and `images.maximumDiskCacheS...
• f88cee9 Backport: Fix(pages-router): restore Content-Length and ETag for /_next/data/...
• cfd5f53 v15.5.13
• 15f2891 [backport]: fix: patch http-proxy to prevent request smuggling in rewrites (#...
• See full diff in compare view

[changeset-bot]

⚠️ No Changeset found

Latest commit: 19bf7a1

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Obfuscated code: npm @react-native/debugger-frontend is 96.0% likely obfuscated Confidence: 0.96 Location: Package overview From: pnpm-lock.yaml → npm/@react-native/debugger-frontend@0.76.9 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@react-native/debugger-frontend@0.76.9. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​types/​jsdom@​21.1.6
	@​types/​react-dom@​18.2.17
	@​react-navigation/​bottom-tabs@​7.2.1
	@​react-navigation/​native@​7.0.15
	@​types/​applepayjs@​14.0.9
	@​types/​googlepay@​0.7.10
	@​types/​jest@​28.1.8
	@​types/​react@​18.3.18
	crc-32@​1.2.2
	@​types/​node@​24.10.10
	@​vitejs/​plugin-basic-ssl@​2.1.4
	@​rollup/​plugin-node-resolve@​16.0.0
	@​rollup/​plugin-typescript@​12.1.2
	rollup@​4.59.0
	@​swc/​core@​1.4.11
	@​vitejs/​plugin-react@​4.7.0
	@​peculiar/​webcrypto@​1.5.0
	@​testing-library/​react-native@​13.2.0
	@​playwright/​test@​1.57.0

View full report

[matt-evervault]

Review summary — safe to merge ✅

No code changes were needed. Nothing was pushed to the branch.

Where next is used in this repo

• The only consumer is examples/next-3ds (verified by grepping every package.json in the workspace).
• It's pulled in via the pnpm workspace catalog ("next": "catalog:"), so the only required edit is the catalog spec — which is exactly what this PR does.
• Surfaces touched by the example:
  • next/font/google, next/image, next/types (Metadata) in app/layout.tsx
  • next/navigation redirect from a "use server" Server Action in app/actons.server.ts
  • App Router pages in app/page.tsx, app/success/page.tsx
  • Empty next.config.mjs — no rewrites, no images.*, no experimental flags

Changelog walk (15.5.12 → 15.5.15)

• 15.5.13 — security backport: patches http-proxy to prevent request smuggling in rewrites (CVE-2026-29057). The example has no rewrites, so this codebase was not exposed, but the patch is desirable.
• 15.5.14 — bug fixes / one opt-in feature:
  • feat(next/image): LRU disk cache + images.maximumDiskCacheSize (opt-in, no config change here, no behaviour change).
  • fix(pages-router): restore Content-Length/ETag for /_next/data/ JSON. Example uses App Router only, so neither affected nor at risk.
• 15.5.15 — security backport: CVE-2026-23869 — crafted requests to React Server Components / Server Function endpoints (App Router, 13.x–16.x) can cause excessive CPU consumption (DoS via deserialization). The example does use App Router + Server Actions, so this is the most relevant fix and the strongest reason to merge.

All three are patch-level, security/bugfix-only backports — Vercel explicitly notes they do not include canary features. No public API changes that affect any surface this repo uses.

Diff sanity

• Only pnpm-workspace.yaml (catalog spec ^15.5.12 → ^15.5.15) and pnpm-lock.yaml change.
• Lockfile side-effect: caniuse-lite deduped to a single resolved copy (1.0.30001777) — pure cleanup.
• No new transitive deps, no new postinstall/scripts. Lockfile deprecation comments on tar@6.2.1 / uuid@7,8 are registry annotations, not introduced by this PR.

Local verification

• pnpm install --frozen-lockfile ✅
• pnpm build (workspace @evervault/* filter) ✅
• pnpm --filter example-next-3ds build (next build end-to-end) ✅ — produced static routes for /, /success, /_not-found with no errors. The pre-existing autoprefixer/flex-end warning and next build's automatic tsconfig.json target: ES2017 rewrite are both unrelated to this bump (same behaviour on 15.5.12).
• CI on the PR is fully green (lint+test, all e2e shards, CodeQL, Socket).

Verdict

Safe to merge as-is. The most relevant CVE for our usage (15.5.15 / CVE-2026-23869) directly mitigates a Server-Actions DoS vector that the next-3ds example exercises.

---

Generated by Claude Code