How many CVEs have patched upstreamTimedOut?

1 published CVEs changed upstreamTimedOut in vercel/next.js, in 1 distinct patches totalling 282 changed lines, between 2026 and 2026.

What is the latest CVE that changed upstreamTimedOut?

CVE-2026-94483 (Next.js: Server-Side Request Forgery in Image Optimization), published 2026-10-02, changed lines 884 to 1163 of packages/next/src/server/image-optimizer.ts.

How does upstreamTimedOut compare to the rest of vercel/next.js?

vercel/next.js has 39 CVEs with a located fix in total; 1 of them changed upstreamTimedOut.

What do the line numbers refer to?

Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

RadicalNotion.AI

Log in Create an account

vercel/next.js

Function

upstreamTimedOut

Name: upstreamTimedOut in vercel/next.js: CVE fixes
Creator: RadicalNotion.AI
License: https://creativecommons.org/licenses/by-nc/4.0/

packages/next/src/server/image-optimizer.ts

Last patched October 2, 2026

1

CVEs

That changed this function

1

Distinct patches

Backports counted once

282

Lines changed

Added plus removed

2026

Years

By CVE publication date

Overview

upstreamTimedOut in vercel/next.js was changed by 1 published CVE fixes in 2026, in 1 distinct patches that added or removed 282 lines in total.

vercel/next.js has 39 CVEs with a located fix in total, so 3% of them touched this function.

CVEs that patched it

Every published CVE whose fix changed upstreamTimedOut, newest first, with the lines each fix touched.

Next.js: Server-Side Request Forgery in Image Optimization
CVE-2026-94483 · lines 884–1163 · +272 −10
High · CVSS 8.3
EPSS 0.2%2026-10-02

Get an alert when the next CVE fix lands in vercel/next.js, with the patched functions.

Monitor next.js CVEs

Other functions in these files

Functions in the same file that CVE fixes also changed.

Other hotspots in the repository

Functions in vercel/next.js changed by the most CVE fixes.

createRedirectRenderResult2 CVEs · packages/next/src/server/app-render/action-handler.ts createPatchedFetcher2 CVEs · packages/next/src/server/lib/patch-fetch.ts handleAction2 CVEs · packages/next/src/server/app-render/action-handler.ts initialize2 CVEs · packages/next/src/server/lib/router-server.ts exportPageImpl2 CVEs · packages/next/src/export/worker.ts exportPagesPage2 CVEs · packages/next/src/export/routes/pages.ts

All patched functions in vercel/next.js

Frequently asked questions

Common questions about CVE fixes to upstreamTimedOut.

How many CVEs have patched upstreamTimedOut?: 1 published CVEs changed upstreamTimedOut in vercel/next.js, in 1 distinct patches totalling 282 changed lines, between 2026 and 2026.
What is the latest CVE that changed upstreamTimedOut?: CVE-2026-94483 (Next.js: Server-Side Request Forgery in Image Optimization), published 2026-10-02, changed lines 884 to 1163 of packages/next/src/server/image-optimizer.ts.
How does upstreamTimedOut compare to the rest of vercel/next.js?: vercel/next.js has 39 CVEs with a located fix in total; 1 of them changed upstreamTimedOut.
What do the line numbers refer to?: Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

References

Fix locations are computed by RadicalNotion.AI from the upstream patch diff of each CVE. CVE data is sourced from the CVE Program.

Track vercel/next.js CVEs

Get an alert when a new CVE lands in this repository, with the patched functions and AI-written remediation guidance.

Create an account See pricing