# Remediation Handoff: CVE-2026-64642

## Summary

NVD: Next.js is a React framework for building full-stack web applications. NVD: In versions 16.0.0 through 16.2.10, crafted requests targeting Next.js applications using App Router built with Turbopack and a single entry in config.i18n.locales can bypass middleware/proxy based authentication. NVD: This issue has been fixed in version 16.2.11.

## Why it matters

CVSS severity is HIGH with score 8.3. EPSS percentile is 0.57723. KEV status is not listed in KEV. Use this as a defensive priority handoff, not as an execution instruction.

## Affected context

* Vendor: vercel
* Product: next.js
* Component: unknown
* Version / CPE / PURL: unknown

## Remediation context

* Recommended route: vendor_patch_or_mitigation
* Vendor/advisory reference: official_reference_present
* Patch status: confirmed
* Fixed version: version
* References: https://github.com/vercel/next.js/commit/6bf4df14508ad6c0cd46af50c6051ee42f2d9151, https://github.com/vercel/next.js/pull/96014, https://github.com/vercel/next.js/releases/tag/v16.2.11, https://github.com/vercel/next.js/security/advisories/GHSA-6gpp-xcg3-4w24

## Human checklist

* Confirm whether the listed product or package is present.
* Confirm affected version.
* Review vendor advisory or official source.
* Confirm patch, fixed version, mitigation, workaround, or monitor-only decision.
* Confirm exposure.
* Document remediation status.

## Safe AI / Codex handoff

* Goal: Prepare a defensive remediation plan for CVE-2026-64642 using only provided public-safe source context and any separate repo context supplied by the user.
* Allowed actions: summarize vendor guidance, prepare a defensive remediation plan, identify affected dependencies only when repo context is separately provided by the user, suggest tests and validation steps, document human verification questions
* Disallowed actions: generate offensive code, provide payloads, scan external targets, change production systems, merge or deploy changes, create GitHub issues or pull requests without explicit separate approval
* Acceptance criteria: Affected product or dependency presence is confirmed by a human., Affected version is confirmed or marked not applicable., Official advisory or source reference is reviewed., Patch, fixed version, mitigation, workaround, or monitor-only decision is documented., Validation steps are proposed without external scanning or production mutation.
* Human approval required: true

## Safety note

This handoff is for defensive triage and remediation planning only. It excludes offensive procedure, payload material, external target scan guidance, and auto-remediation.