{"id":"INC-vercel-3h7jsmmrljwt","kind":"incident","aliases":[],"related":[],"title":"Vercel: Resolved: Elevated ERR_STREAM_PREMATURE_CLOSE errors in Vercel Functions","description":"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.\n\nAs 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\n\nWe 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.","summary":"A 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.","severity":"low","cvss":null,"epss":null,"exploited":false,"exploited_at":null,"products":[{"name":"Vercel","fixed":[],"affected":"","ecosystem":"vendor"}],"ecosystems":["vendor"],"tags":["hosting","incident","next.js","node-fetch","node.js","security","vendor","vercel"],"not_affected_if":["not-using-node-fetch-v2","outside-incident-window"],"how_to_check":"- Look for ERR_STREAM_PREMATURE_CLOSE errors in Vercel Function logs from June 19 09:09 to 16:16 UTC\n- Check whether your functions depend on `node-fetch@2` (`npm ls node-fetch`)","fix":"- No action required according to Vercel; the Node.js upgrade was reverted and functions are operating normally\n- Monitor for the upstream fix tracked at https://github.com/nodejs/node/issues/63989 before Vercel re-lands the Node.js upgrade","status":"resolved","published_at":"2026-06-19T17:54:16+00:00","first_seen_at":"2026-10-23T19:12:22+00:00","triaged_at":"2026-10-25T05:31:18+00:00","updated_at":"2026-10-25T05:31:18+00:00","category":"vendor","confidence":0.7,"triage":{"at":"2026-10-25T05:31:18Z","model":"claude-haiku-5-5","output":{"fix":"- No action required according to Vercel; the Node.js upgrade was reverted and functions are operating normally\n- Monitor for the upstream fix tracked at https://github.com/nodejs/node/issues/63989 before Vercel re-lands the Node.js upgrade","reach":"internet","title":"Vercel: Node.js upgrade broke node-fetch@2 streaming in Functions","impact":"low","summary":"A 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.","category":"vendor","nicknames":[],"who_cares":["vercel","node.js","node-fetch","next.js"],"confidence":0.7,"needs_auth":"no","worst_case":"Intermittent function invocation errors; no code execution or data exposure reported","analyst_note":"","how_to_check":"- Look for ERR_STREAM_PREMATURE_CLOSE errors in Vercel Function logs from June 19 09:09 to 16:16 UTC\n- Check whether your functions depend on `node-fetch@2` (`npm ls node-fetch`)","needs_analyst":false,"not_affected_if":["not-using-node-fetch-v2","outside-incident-window"],"who_is_affected":"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.","user_interaction":"no","needs_special_setup":"no","severity_if_unknown":"low"},"cost_usd":0.000655,"input_tokens":3473,"output_tokens":616,"severity_before":"low"},"analyst_status":null,"analyst_note":null,"search":"'/nodejs/node/issues/63989':141C '09':53B,54B,76C,77C '16':56B,57B,79C,80C '19':52B,75C '2':49B,91C,134C '2026':110C '3h7jsmmrljwt':15A 'action':70B,155C 'affect':158C 'began':114C 'break':127C 'caus':36B,136C 'close':7A,41B,104C 'contain':122C 'custom':69B 'elev':3A 'err':4A,38B,101C 'error':8A,42B,97C,138C 'experienc':94C 'fetch':22B,48B,90C,133C 'fix':177C 'function':11A,35B,44B,86C,159C 'github.com':140C 'github.com/nodejs/node/issues/63989':139C 'host':17B 'inc':13A 'inc-vercel-3h7jsmmrljwt':12A 'incid':18B 'intermitt':37B,95C 'invoc':96C 'issu':146C,175C 'jun':74C 'june':51B,109C 'land':168C 'may':92C 'new':117C 'next.js':19B 'node':21B,47B,89C,132C 'node-fetch':20B,46B,88C,131C 'node.js':23B,28B,64B,108C,118C,152C,170C 'normal':163C 'oper':162C 'part':106C 'prematur':6A,40B,103C 'previous':63B,151C 're':167C 're-land':166C 'regress':125C 'releas':30B,112C 'requir':72B,157C 'resolv':2A,144C 'respons':128C 'revert':60B,148C 'roll':31B,115C 'say':67B 'secur':24B,29B,111C 'stream':5A,39B,102C,129C 'subset':83C 'surfac':99C 'upgrad':171C 'upstream':124C,174C 'use':45B,87C 'utc':58B,81C 'vendor':25B 'vercel':1A,10A,14A,16A,26B,34B,59B,85C 'version':65B,119C,121C,153C","nicknames":[],"mitigations":[],"who_affected":"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.","tier":"C","verified":{},"analyst_revisit_at":null,"first_public_at":"2026-06-19T17:54:16+00:00","kev":null,"cvss_vector":null,"cvss_by":null,"poc_count":0,"sources":[{"source":"statuspage","external_id":"vercel:3h7jsmmrljwt","url":"https://stspg.io/clqq0f551l8m","severity":"low","published_at":"2026-06-19T17:54:16+00:00","modified_at":"2026-06-19T17:59:13+00:00","first_seen_at":"2026-10-23T19:12:22+00:00","fetched_at":"2026-10-25T20:39:56+00:00","note":null}],"documents":[],"notice":"Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai"}