Defined in 3 files
Last patched
getResponseCache in vercel/next.js was changed by 2 published CVE fixes in 2026, in 4 distinct patches that added or removed 28 lines in total.
The name occurs in 3 files: packages/next/src/server/route-modules/route-module.ts, packages/next/src/server/base-server.ts, packages/next/src/server/next-server.ts.
vercel/next.js has 39 CVEs with a located fix in total, so 5% of them touched this function.
Every published CVE whose fix changed getResponseCache, newest first, with the lines each fix touched.
CVE-2026-94484 · packages/next/src/server/base-server.ts · line 396 · +0 −4
CVE-2026-94484 · packages/next/src/server/next-server.ts · lines 537–542 · +1 −4
CVE-2026-94484 · packages/next/src/server/route-modules/route-module.ts · lines 860–863 · +4 −1
CVE-2026-94543 · packages/next/src/server/base-server.ts · line 396 · +0 −4
CVE-2026-94543 · packages/next/src/server/next-server.ts · lines 537–542 · +1 −4
CVE-2026-94543 · packages/next/src/server/route-modules/route-module.ts · lines 860–863 · +4 −1
Get an alert when the next CVE fix lands in vercel/next.js, with the patched functions.
Monitor next.js CVEsFunctions in the same files that CVE fixes also changed.
Functions in vercel/next.js changed by the most CVE fixes.
Common questions about CVE fixes to getResponseCache.
Fix locations are computed by RadicalNotion.AI from the upstream patch diff of each CVE. CVE data is sourced from the CVE Program.
Get an alert when a new CVE lands in this repository, with the patched functions and AI-written remediation guidance.
