Skepra / Web recovery & resilience
Next.js self-hosted response forwarding.
When a client portal forwards an upstream response, application and proxy owners need one shared applicability and recovery record.
Discuss the next maintenance decisionWhat the advisory says
The Next.js maintainer published GHSA-pc58-hwjq-p385, CVE-2026-119348, on 3 November 2026. Self-hosted applications that return a fetched upstream Response unchanged can emit mismatched framing. The described risk requires an HTTP/1.1 reverse proxy that permits pipelined response queueing on a shared backend connection.
Affected versions include 16.0.0 through 16.4.4 and versions at or below 15.5.28; the listed fixes are 16.4.5 and 15.5.29.
Build one route map
Record the browser route, Next.js handler, upstream owner and each proxy hop. Establish whether the fetched Response is returned unchanged and ask the hosting owner to confirm the relevant HTTP/1.1 connection behavior. A product name alone does not prove the condition.
Retest the business flow
In staging, use two synthetic accounts and distinguishable documents through the same route and proxy path. Cover success, upstream error, redirect handling and interrupted downloads where supported. Record the patched artifact and the responsible application and hosting reviewers.
Limits and handoff
This page does not claim a customer incident, proxy exposure or response desynchronization. Its practical output is a split-owner route map and bounded regression/handoff record.