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

CVE-2026-45109Next.js: Middleware / Proxy bypass in App Router applications via segment-prefetch routes

Routine No exploitation evidence; EPSS 0.9%.

CVE-2026-45109 is not known to be exploited in the wild. EPSS estimates a 0.9% chance of exploitation in the next 30 days, higher than 59% of all CVEs. This Next.js vulnerability: CVSS 7.5 (v3.1), attacks can be automated. Fixed upstream in Next.js 16.2.6, 15.5.18. Routine: patch when convenient.

Share this

Remediation#

Fixed upstream in Next.js 16.2.6, 15.5.18.

Patch events

  1. This monthSecurity release

    Web frameworkNext.js

    Next.js security releases: 16.2.6, 15.5.18

    Upgrade to 16.2.615.5.18

    Why: Vendor security release for server software (most severe: CVE-2026-45109).

Exploit intelligence#

SignalValueSource
Known exploitedNoCISA KEV
Ransomware use—CISA KEV
EPSS (30-day exploitation probability)0.9% (59th pct)FIRST EPSS v2026.06.15
CVSS base score7.5 (v3.1)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
CNA / CISA ADP
SSVC exploitationnoneCISA Vulnrichment
SSVC automatableYesCISA Vulnrichment
SSVC technical impactpartialCISA 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.2.0 to before 15.5.18 and 16.2.6, it was found that the fix addressing CVE-2026-44575 did not apply to middleware.ts with Turbopack. This vulnerability is fixed in 15.5.18 and 16.2.6.

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 →