1-minute read
What a defender needs to know
Next.js released 15.5.24 and 16.3.3 to fix two critical unauthenticated remote-code-execution paths. One reaches the libheif decoder when the Image Optimization API handles an attacker-controlled AVIF image. The other affects Windows-hosted applications that use both the Pages Router and App Router without Cache Components.
Linux and macOS are outside the Windows-specific flaw. The vendor does not report exploitation, victims, or the number of exposed deployments. Self-hosted operators remain responsible for upgrading and redeploying every instance.
Run node -p "require('next/package.json').version" and node -p "process.platform" inside each production instance across production. Inventory AVIF optimization, attacker-controlled image sources, applications with both routing systems, and Windows servers without Cache Components. Review /_next/image requests, optimizer failures, restarts, unexpected files, and child processes launched by node.exe during the vulnerable interval.
The verification target is Next.js 15.5.24 or 16.3.3 on every running process, no superseded instance serving traffic, no AVIF input entering the old optimization behavior, and no unexplained child process or filesystem change. A staged AVIF request establishes exposure to processing; it does not establish code execution.