CVE-2026-64648

MEDIUMNVD 5.45.4—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.4 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 73% 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, nvd
Trending — 3 sources updated this week
5.4EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.4Exploit: None knownExposed: 0

A fix is available — apply it.

Next.js is a React framework for building full-stack web applications. In versions 12.0.0 through 15.5.20 and 16.0.0 through 16.2.10, a server-side fetch with a request body may return a cached response body from a different request to the same URL but different body. Confidential data in the POST's response body would then leak to unauthorized requests. Though the request itself will not be deduped. This only applies to fetch calls with a request that has a different init than the one passed to fetch. A safe request would be: fetch(new Request(init), init). An unsafe request would be: fetch(new Request(init), aDifferentInit). This issue has been fixed in versions 15.5.21 and 16.2.11.

CVSS v3
5.4
EG Score
5.4(medium)
EG Risk
24(Track)
EG Risk 24/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
Severity54% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
27%
KEV
Not listed

Published

July 22, 2026

Last Modified

July 29, 2026

Advisory Details (5)

Auto-updated Jul 27, 2026
Patch available. Sources: github, github_commit, github_release.
github_release Patch Available

v16.2.11

Patch available: vercel/next.js v16.2.11

https://github.com/vercel/next.js/releases/tag/v16.2.11
github_release Patch Available

v15.5.21

Patch available: vercel/next.js v15.5.21

https://github.com/vercel/next.js/releases/tag/v15.5.21
github_commit Patch Available

commit 73b94872bc34 (vercel/next.js)

Patch available: vercel/next.js v16.2.11 (contains commit 73b94872bc34)

https://github.com/vercel/next.js/commit/73b94872bc343d09494b50394d8c08eb9fc8e56a
github_commit Patch Available

commit 062f66700b52 (vercel/next.js)

Patch available: vercel/next.js v15.5.21 (contains commit 062f66700b52)

https://github.com/vercel/next.js/commit/062f66700b52a5d6bba2c0605d55577ab7ad262c
github Patch Available

Cache confusion of response bodies for requests with bodies · Advisory · vercel/next.js · GitHub

https://github.com/vercel/next.js/security/advisories/GHSA-68g3-v927-f742

Vendor Advisories for CVE-2026-64648(2)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatnext2026-08-12redhat

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.11—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 13× in last 7d / 66× 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 124 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-64648?
CVE-2026-64648 is a medium vulnerability published on July 22, 2026. Next.js is a React framework for building full-stack web applications. In versions 12.0.0 through 15.5.20 and 16.0.0 through 16.2.10, a server-side fetch with a request body may return a cached response body from a different request to the same URL but different body. Confidential data in the…
When was CVE-2026-64648 disclosed?
CVE-2026-64648 was first published in the National Vulnerability Database on July 22, 2026, with the most recent update on July 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64648 actively exploited?
CVE-2026-64648 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 72.9% of all scored CVEs.
What is the CVSS score of CVE-2026-64648?
CVE-2026-64648 has a CVSS v3 base score of 5.4 (NVD).
How do I remediate CVE-2026-64648?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64648, 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-64648

Explore →

Is Your Infrastructure Affected by CVE-2026-64648?

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

Start Free Scan →Browse All CVEs