CVE-2026-45109

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.6%, top 55% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
49(Track)
EG Risk 49/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
45%
KEV
Not listed

Published

May 13, 2026

Last Modified

August 13, 2026

Advisory Details (1)

Auto-updated May 13, 2026
Patch available. Sources: github.
github Patch Available

Middleware / Proxy bypass in App Router applications via segment-prefetch routes - Incomplete Fix Follow-Up · Advisory · vercel/next.js · GitHub

https://github.com/vercel/next.js/security/advisories/GHSA-26hh-7cqf-hhc6

Vendor Advisories for CVE-2026-45109(4)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatnext2026-08-12redhat
redhatrhtas/rekor-search-ui-rhel9:17839586222026-07-16redhat
redhatrhtas/rekor-search-ui-rhel9:17833271852026-07-09redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
next—16.2.6—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 31× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 171 total refreshes for this CVE.

  1. 2026-09-13 16:47 UTCEPSS rescore
  2. 2026-09-12 15:01 UTCEPSS rescore
  3. 2026-09-11 14:53 UTCEPSS rescore
  4. 2026-09-11 09:37 UTCEPSS rescore
  5. 2026-09-11 08:23 UTCOSV refresh
  6. 2026-09-10 09:34 UTCEPSS rescore
  7. 2026-09-08 22:00 UTCEPSS rescore
  8. 2026-09-07 16:01 UTCEPSS rescore
  9. 2026-09-06 13:47 UTCEPSS rescore
  10. 2026-09-04 05:06 UTCEPSS rescore
  11. 2026-09-02 14:12 UTCEPSS rescore
  12. 2026-09-01 13:54 UTCEPSS rescore
  13. 2026-08-30 19:17 UTCEPSS rescore
  14. 2026-08-30 01:22 UTCEPSS rescore
  15. 2026-08-28 21:41 UTCEPSS rescore
  16. 2026-08-27 14:25 UTCEPSS rescore
  17. 2026-08-26 14:46 UTCEPSS rescore
  18. 2026-08-25 13:49 UTCEPSS rescore
  19. 2026-08-23 17:51 UTCEG score recompute
  20. 2026-08-23 17:51 UTCVendor advisory
  21. 2026-08-23 00:19 UTCEPSS rescore
  22. 2026-08-21 23:49 UTCEPSS rescore
  23. 2026-08-20 22:55 UTCEPSS rescore
  24. 2026-08-20 19:48 UTCEG score recompute
  25. 2026-08-20 19:48 UTCVendor advisory
Show 75 more
  1. 2026-08-19 17:04 UTCEPSS rescore
  2. 2026-08-18 13:48 UTCEPSS rescore
  3. 2026-08-17 13:47 UTCEPSS rescore
  4. 2026-08-17 10:39 UTCEG score recompute
  5. 2026-08-17 10:39 UTCVendor advisory
  6. 2026-08-16 14:56 UTCEPSS rescore
  7. 2026-08-16 04:03 UTCEG score recompute
  8. 2026-08-16 04:03 UTCVendor advisory
  9. 2026-08-16 02:14 UTCEPSS rescore
  10. 2026-08-15 01:30 UTCEPSS rescore
  11. 2026-08-14 15:07 UTCVendor advisory
  12. 2026-08-14 02:32 UTCEG score recompute
  13. 2026-08-14 02:32 UTCVendor advisory
  14. 2026-08-13 22:00 UTCEPSS rescore
  15. 2026-08-13 13:38 UTCEG score recompute
  16. 2026-08-13 13:38 UTCVendor advisory
  17. 2026-08-13 12:28 UTCEG score recompute
  18. 2026-08-13 12:28 UTCVendor advisory
  19. 2026-08-13 04:25 UTCVendor advisory
  20. 2026-08-12 15:50 UTCEG score recompute
  21. 2026-08-12 15:50 UTCVendor advisory
  22. 2026-08-12 13:51 UTCEPSS rescore
  23. 2026-08-11 15:28 UTCEG score recompute
  24. 2026-08-11 15:28 UTCVendor advisory
  25. 2026-08-11 00:57 UTCEG score recompute
  26. 2026-08-11 00:57 UTCVendor advisory
  27. 2026-08-11 00:00 UTCEPSS rescore
  28. 2026-08-10 03:06 UTCVendor advisory
  29. 2026-08-09 14:31 UTCEG score recompute
  30. 2026-08-09 14:31 UTCVendor advisory
  31. 2026-08-09 13:46 UTCEPSS rescore
  32. 2026-08-09 01:55 UTCEG score recompute
  33. 2026-08-09 01:55 UTCVendor advisory
  34. 2026-08-08 16:37 UTCEPSS rescore
  35. 2026-08-08 02:34 UTCEG score recompute
  36. 2026-08-08 02:34 UTCVendor advisory
  37. 2026-08-07 13:58 UTCVendor advisory
  38. 2026-08-07 01:23 UTCEG score recompute
  39. 2026-08-07 01:23 UTCVendor advisory
  40. 2026-08-06 13:46 UTCEPSS rescore
  41. 2026-08-06 10:17 UTCVendor advisory
  42. 2026-08-05 21:40 UTCEG score recompute
  43. 2026-08-05 21:40 UTCVendor advisory
  44. 2026-08-05 19:17 UTCEPSS rescore
  45. 2026-08-04 15:10 UTCEPSS rescore
  46. 2026-08-04 10:38 UTCEPSS rescore
  47. 2026-08-03 19:09 UTCEG score recompute
  48. 2026-08-03 19:09 UTCVendor advisory
  49. 2026-08-03 10:36 UTCEPSS rescore
  50. 2026-08-02 21:03 UTCVendor advisory
  51. 2026-08-02 08:27 UTCEG score recompute
  52. 2026-08-02 08:27 UTCVendor advisory
  53. 2026-08-02 02:27 UTCEPSS rescore
  54. 2026-08-01 19:51 UTCEG score recompute
  55. 2026-08-01 19:51 UTCVendor advisory
  56. 2026-08-01 04:16 UTCEPSS rescore
  57. 2026-07-30 16:28 UTCEPSS rescore
  58. 2026-07-30 01:30 UTCEPSS rescore
  59. 2026-07-28 15:36 UTCEPSS rescore
  60. 2026-07-27 14:13 UTCEPSS rescore
  61. 2026-07-26 14:54 UTCEPSS rescore
  62. 2026-07-26 14:54 UTCEPSS rescore
  63. 2026-07-25 14:18 UTCEPSS rescore
  64. 2026-07-24 14:17 UTCEPSS rescore
  65. 2026-07-23 14:18 UTCEPSS rescore
  66. 2026-07-23 03:16 UTCEG score recompute
  67. 2026-07-22 14:08 UTCEPSS rescore
  68. 2026-07-21 15:24 UTCEPSS rescore
  69. 2026-07-20 17:08 UTCEPSS rescore
  70. 2026-07-19 14:31 UTCEPSS rescore
  71. 2026-07-19 02:29 UTCEPSS rescore
  72. 2026-07-18 10:04 UTCEPSS rescore
  73. 2026-07-18 02:29 UTCOSV refresh
  74. 2026-07-16 17:03 UTCEPSS rescore
  75. 2026-07-15 16:57 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-45109?
CVE-2026-45109 is a high vulnerability published on May 13, 2026. 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.
When was CVE-2026-45109 disclosed?
CVE-2026-45109 was first published in the National Vulnerability Database on May 13, 2026, with the most recent update on August 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-45109 actively exploited?
CVE-2026-45109 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 54.6% of all scored CVEs.
What is the CVSS score of CVE-2026-45109?
CVE-2026-45109 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-45109?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-45109, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-45109

Explore →

Is Your Infrastructure Affected by CVE-2026-45109?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs