vercel · Next.js · published 2026-05-13

CVE-2026-44574Next.js: Middleware / Proxy bypass through dynamic route parameter injection

Routine No exploitation evidence; EPSS 0.6%.

CVE-2026-44574 is not known to be exploited in the wild. EPSS estimates a 0.6% chance of exploitation in the next 30 days, higher than 51% of all CVEs. This Next.js vulnerability: CVSS 8.1 (v3.1), a successful attack gives total control of the component. Fixed upstream in Next.js 16.2.5, 15.5.16. Routine: patch when convenient.

Share this

Remediation#

Fixed upstream in Next.js 16.2.5, 15.5.16.

Patch events

  1. This monthSecurity release

    Web frameworkNext.js

    Next.js security releases: 16.2.5, 15.5.16

    Upgrade to 16.2.515.5.16

    Why: CVE-2026-44578: EPSS 36% with high severity (CVSS 8.6).

Exploit intelligence#

SignalValueSource
Known exploitedNoCISA KEV
Ransomware use—CISA KEV
EPSS (30-day exploitation probability)0.6% (51th pct)FIRST EPSS v2026.06.15
CVSS base score8.1 (v3.1)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
CNA / CISA ADP
SSVC exploitationnoneCISA Vulnrichment
SSVC automatableNoCISA Vulnrichment
SSVC technical impacttotalCISA Vulnrichment

Affected versions (from the CVE record)#

Description (from the CVE record)#

Next.js is a React framework for building full-stack web applications. From 15.4.0 to before 15.5.16 and 16.2.5, applications that rely on middleware to protect dynamic routes can be vulnerable to authorization bypass. In affected deployments, specially crafted query parameters can alter the dynamic route value seen by the page while leaving the visible path unchanged, which can allow protected content to be rendered without passing the expected middleware check. This vulnerability is fixed in 15.5.16 and 16.2.5.

Quoted from the CVE Program record.

Elsewhere#

Distro status: Debian · Ubuntu · Red Hat · Alpine

Something wrong on this page?
Anonymous. Reports are checked against the primary source.

Also on today's list

See today's list → · Coming up →