How many CVEs have patched _getPathname?

2 published CVEs changed _getPathname in vercel/next.js, in 2 distinct patches totalling 8 changed lines, between 2026 and 2026.

What is the latest CVE that changed _getPathname?

CVE-2026-94484 (Next.js: Cache poisoning in Next.js SSG/ISR rendering leads to cross-user content substitution and persistent denial of service), published 2026-10-02, changed lines 311 of packages/next/src/server/lib/incremental-cache/index.ts.

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

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

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

_getPathname

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

packages/next/src/server/lib/incremental-cache/index.ts

Last patched October 2, 2026

2

CVEs

That changed this function

2

Distinct patches

Backports counted once

8

Lines changed

Added plus removed

2026

Years

By CVE publication date

Overview

_getPathname in vercel/next.js was changed by 2 published CVE fixes in 2026, in 2 distinct patches that added or removed 8 lines in total.

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

CVEs that patched it

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

Next.js: Cache poisoning in Next.js SSG/ISR rendering leads to cross-user content substitution and persistent denial of service
CVE-2026-94484 · line 311 · +0 −4
Medium · CVSS 6.3
EPSS 0.2%2026-10-02
Next.js: Cache poisoning of SSG and ISR pages in self-hosted Next.js applications
CVE-2026-94543 · line 311 · +0 −4
Medium · CVSS 6.3
EPSS 0.3%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 _getPathname.

How many CVEs have patched _getPathname?: 2 published CVEs changed _getPathname in vercel/next.js, in 2 distinct patches totalling 8 changed lines, between 2026 and 2026.
What is the latest CVE that changed _getPathname?: CVE-2026-94484 (Next.js: Cache poisoning in Next.js SSG/ISR rendering leads to cross-user content substitution and persistent denial of service), published 2026-10-02, changed lines 311 of packages/next/src/server/lib/incremental-cache/index.ts.
How does _getPathname compare to the rest of vercel/next.js?: vercel/next.js has 39 CVEs with a located fix in total; 2 of them changed _getPathname.
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