Breaking News: Thousands Of GitHub Accounts Hijacked With wfx-loot CI Secret
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2026-45109

next.js: Next.js: Information disclosure via security fix bypass in middleware with Turbopack

Overview

Published
13 May 2026
Modified
4 Nov 2026
High CVE
3 Registry packages
4 OS packages
3 Linux distributions
Yes Fix available

Description

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.

Source: OX vulnerability database

Severity

7.5 · HIGH

CVSS 3.1 base score, scored by NVD.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Weakness: CWE-288, CWE-358

Affected packages · 3

Packages affected by CVE-2026-45109
EcosystemPackageVulnerableFixed in
npm next >=15.2.0, <15.5.18>=16.0.0, <16.2.6 15.5.1816.2.6
Seal npm @seal-security/next >=16.0.6-sp1, <16.0.6-sp999 16.0.6-sp999
Seal npm next >=16.0.6-sp0, <16.0.6-sp999 16.0.6-sp999

Open a package to see all its vulnerabilities.

Operating systems · 5 fixes

chainguard 1 release · 2 packages

fixed 2
keep jitsucom-jitsu
chainguard fixes for CVE-2026-45109
ReleasePackageFixed in
keep 0.51.0-r7
jitsucom-jitsu 2.11.0-r24

minimos 1 release · 2 packages

fixed 2
peerdb-ui trigger-dev
minimos fixes for CVE-2026-45109
ReleasePackageFixed in
peerdb-ui 0.36.25-r0
trigger-dev 4.5.0-r0

wolfi 1 release · 1 package

fixed 1
jitsucom-jitsu
wolfi fixes for CVE-2026-45109
ReleasePackageFixed in
jitsucom-jitsu 2.11.0-r24

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.