fix(security): Fix security issue in next via minor version upgrade from 15.4.8 to 15.5.24

[aikido-autofix]

Upgrade Next.js to fix critical RCE in AVIF image optimization, SSRF in WebSocket requests, DoS via connection exhaustion and CPU exhaustion in Server Functions, and disable AVIF optimization until patched.

✅ Code not affected by breaking changes.

✅ No breaking changes from the Next.js 15.4.8 => 15.5.24 upgrade affect this codebase.

The codebase contains a Next.js demo application (packages/demo-nextjs) that uses:

• Basic Next.js routing (App Router and Pages Router)

• Client components with 'use client' directive

• Standard Next.js hooks (useRouter, useSearchParams)

• No experimental features

• No Next.js configuration file (using defaults)

• No server components that use cookies() or headers()

• No MDX components

• No AMP pages

• No unstable_rootParams usage

• No middleware

All breaking changes listed in the changelog (removal of experimental.dynamicIO, useMDXComponents, experimental.strictNextHead, sync access restrictions for cookies/headers, Turbopack changes, AMP deprecation, unstable_rootParams deprecation, and middleware stabilization) do not impact any code in this repository.

All breaking changes by upgrading next from version 15.4.8 to 15.5.24 (CHANGELOG)

Version	Description
15.5.0	refactor: rename experimental.dynamicIO to experimental.cacheComponents: #81562
15.5.0	Remove useMDXComponents argument: #80871
15.5.0	Remove experimental.strictNextHead: #81882
15.5.0	[Cache Components] Disallow sync access of cookies & headers at runtime: #82564
15.5.0	Turbopack: set window.next.turbopack instead: #82580
15.5.0	[Deprecation Warnings]: add amp deprecation warning: #82551
15.5.0	[Deprecation Warnings]: add unstable_rootParams deprecation warning: #82582
15.5.0	Stabilize node middleware support: #81907

✅ 7 CVEs resolved by this upgrade, including 1 critical 🚨 CVE

This PR will resolve the following CVEs:

Issue	Severity	Description
GHSA-2xp9-vwfh-vxw4	🚨 CRITICAL	[next] A vulnerability in the underlying libheif library used by sharp which Next.js uses for image optimization can lead to remote code execution when AVIF files are optimized. Until a fix has propagated, optimization of AVIF files is disabled.
CVE-2026-44578	HIGH	[next] A server-side request forgery vulnerability in self-hosted Next.js applications allows attackers to craft WebSocket upgrade requests that proxy arbitrary requests to internal or external destinations, potentially exposing internal services or cloud metadata. Vercel-hosted deployments are unaffected.
CVE-2026-44579	HIGH	[next] Applications using Partial Prerendering with Cache Components are vulnerable to connection exhaustion via crafted POST requests to server actions, causing request-body handling deadlocks that consume server resources and lead to denial of service. Malicious actors can exhaust file descriptors and server capacity, preventing legitimate users from accessing the application.
GHSA-q4gf-8mx6-v5v3	HIGH	[next] A specially crafted HTTP request to App Router Server Function endpoints can trigger excessive CPU usage during deserialization, causing denial of service (DoS).
GHSA-8h8q-6873-q5fj	HIGH	[next] A specially crafted HTTP request to App Router Server Function endpoints can trigger excessive CPU usage during deserialization, causing denial of service (DoS).
CVE-2026-29057	MEDIUM	[next] HTTP request smuggling vulnerability in Next.js rewrites with chunked DELETE/OPTIONS requests allows attackers to bypass route restrictions and access unintended backend endpoints. An attacker could smuggle malicious requests to internal or admin routes through request boundary disagreement between proxy and backend.
GHSA-w37m-7fhw-fmv9	MEDIUM	[next] A malicious HTTP request can expose compiled source code of Server Functions in affected React packages and frameworks, potentially revealing business logic through information disclosure.

🤖 Remediation details

Upgrade next to 15.5.24 to remediate multiple security vulnerabilities

Short summary

This PR fixes multiple security vulnerabilities in the next (Next.js) package by upgrading it from 15.4.8 to 15.5.24. The change is applied in two places: the root package.json (where next is declared as a direct devDependency) and the packages/demo-nextjs/package.json workspace member manifest (where it is declared as a direct dependency). The yarn.lock lockfile is updated accordingly, consolidating to a single resolved entry at 15.5.24.

next

next was declared as an exact-pinned direct dependency at 15.4.8 in both the monorepo root package.json and the packages/demo-nextjs workspace manifest. Because both pins were exact (no caret or tilde), a lockfile refresh alone could not pull in a newer version — both manifest entries required explicit edits. The version was updated to 15.5.24 in both locations, which is the minimum release that satisfies all of the patched version floors across the full set of advisories targeting this package (the most demanding being 15.5.24 for the critical-severity advisory). After updating both manifests, yarn install --ignore-engines --ignore-scripts was run from the lockfile root to produce a single consolidated yarn.lock entry at 15.5.24, replacing the previous 15.4.8 entry.

Version changes

Package	From	To	Why updated
next	15.4.8	15.5.24	Direct CVE fix (root package.json + packages/demo-nextjs/package.json)

[pr-auditor]

✅ Security Analysis Results

No security issues found. 3 files reviewed.

---

@pr-auditor rescan to re-run · Powered by Claude Sonnet 5 · Docs · #security-engineering-team