Defined in 2 files
Last patched
IncrementalCache in vercel/next.js was changed by 3 published CVE fixes in 2026, in 6 distinct patches that added or removed 179 lines in total.
The name occurs in 2 files: packages/next/src/server/lib/incremental-cache/index.ts, packages/next/src/server/response-cache/types.ts.
vercel/next.js has 39 CVEs with a located fix in total, so 8% of them touched this function.
Every published CVE whose fix changed IncrementalCache, newest first, with the lines each fix touched.
CVE-2026-94484 · packages/next/src/server/lib/incremental-cache/index.ts · lines 173–824 · +39 −15 in 11 hunks
CVE-2026-94484 · packages/next/src/server/response-cache/types.ts · lines 308–318 · +2 −2 in 2 hunks
CVE-2026-94543 · packages/next/src/server/lib/incremental-cache/index.ts · lines 173–824 · +39 −15 in 11 hunks
CVE-2026-94543 · packages/next/src/server/response-cache/types.ts · lines 308–318 · +2 −2 in 2 hunks
CVE-2026-64647 · packages/next/src/server/lib/incremental-cache/index.ts · lines 403–464 · +37 −26 in 2 hunks
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 IncrementalCache.
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.
