Live › incident › INC-vercel-3h7jsmmrljwt
Go to dashboardA Node.js security release rolled out to Vercel Functions caused intermittent ERR_STREAM_PREMATURE_CLOSE errors for functions using node-fetch@2 between June 19 09:09 and 16:16 UTC. Vercel reverted to the previous Node.js version and says no customer action is required.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 19:12 UTC. All times on this page are UTC.
Vercel Functions that use node-fetch@2 for response streaming were affected during the incident window, when new Node.js versions were rolled out. This is a reliability regression rather than a security exposure, and teams not using node-fetch@2 on Vercel Functions were not affected.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| Vercel | vendor | – | – |
node-fetch@2 (npm ls node-fetch)Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
Between Jun 19 09:09 and 16:16 UTC, a subset of Vercel Functions using node-fetch@2 may have experienced intermittent invocation errors that surfaced as ERR_STREAM_PREMATURE_CLOSE.
As part of Node.js June 2026 security releases, we began rolling out new Node.js versions. Those versions contain an upstream regression that breaks response streaming for node-fetch@2, which caused the errors https://github.com/nodejs/node/issues/63989
We have resolved the issue by reverting to the previous Node.js version. No action is required — affected functions are now operating normally. We will re-land the Node.js upgrade once the upstream issue is fixed.
This page as .md · .json · in your agent: get_signal("INC-vercel-3h7jsmmrljwt")