CVE-2026-64647

MEDIUMNVD 5.45.4—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.4 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 72% 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
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

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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 is only an issue when receiving request bodies with a content type charset other than UTF-8. For example, the UTF-16 byte sequences for 삃삃 and 섄섄 in the request body would share the same cache. 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
28%
KEV
Not listed

Published

July 22, 2026

Last Modified

July 29, 2026

Advisory Details (5)

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

Cache confusion of response bodies for requests with bodies containing invalid UTF-8 byte sequences · Advisory · vercel/next.js · GitHub

https://github.com/vercel/next.js/security/advisories/GHSA-4633-3j49-mh5q
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_pr Patch Available

fix(incremental-cache): byte-exact fetch cache key for binary bodies

Patch available: vercel/next.js v16.3.0-canary.92 (PR #96008 merged 2026-07-21)

https://github.com/vercel/next.js/pull/96008
github_commit Patch Available

commit 025bf4a5f7b4 (vercel/next.js)

Patch available: vercel/next.js v16.3.0-canary.92 (contains commit 025bf4a5f7b4)

https://github.com/vercel/next.js/commit/025bf4a5f7b47fb7758c4ebf1c931a61c451c082

Vendor Advisories for CVE-2026-64647(1)

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

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 7× in last 7d / 42× 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.

  1. 2026-09-13 22:25 UTCEG score recompute
  2. 2026-09-12 21:12 UTCEG score recompute
  3. 2026-09-11 21:12 UTCEG score recompute
  4. 2026-09-11 14:53 UTCEPSS rescore
  5. 2026-09-11 09:37 UTCEPSS rescore
  6. 2026-09-10 21:12 UTCEG score recompute
  7. 2026-09-09 09:11 UTCEG score recompute
  8. 2026-09-08 22:01 UTCEPSS rescore
  9. 2026-09-07 21:39 UTCEG score recompute
  10. 2026-09-07 16:01 UTCEPSS rescore
  11. 2026-09-06 13:47 UTCEPSS rescore
  12. 2026-09-05 19:33 UTCEG score recompute
  13. 2026-09-05 15:31 UTCEPSS rescore
  14. 2026-09-04 13:39 UTCEG score recompute
  15. 2026-09-04 05:07 UTCEPSS rescore
  16. 2026-09-02 14:12 UTCEPSS rescore
  17. 2026-09-01 23:30 UTCEG score recompute
  18. 2026-09-01 13:54 UTCEPSS rescore
  19. 2026-09-01 04:40 UTCEPSS rescore
  20. 2026-08-31 00:48 UTCEG score recompute
  21. 2026-08-30 19:17 UTCEPSS rescore
  22. 2026-08-30 01:22 UTCEPSS rescore
  23. 2026-08-30 00:48 UTCEG score recompute
  24. 2026-08-28 21:42 UTCEPSS rescore
  25. 2026-08-27 21:17 UTCEG score recompute
Show 60 more
  1. 2026-08-26 21:17 UTCEG score recompute
  2. 2026-08-26 14:47 UTCEPSS rescore
  3. 2026-08-25 20:48 UTCEG score recompute
  4. 2026-08-25 13:49 UTCEPSS rescore
  5. 2026-08-24 20:41 UTCEG score recompute
  6. 2026-08-23 20:42 UTCEG score recompute
  7. 2026-08-23 00:19 UTCEPSS rescore
  8. 2026-08-22 20:42 UTCEG score recompute
  9. 2026-08-21 23:49 UTCEPSS rescore
  10. 2026-08-21 20:42 UTCEG score recompute
  11. 2026-08-20 22:55 UTCEPSS rescore
  12. 2026-08-19 20:41 UTCEG score recompute
  13. 2026-08-19 17:04 UTCEPSS rescore
  14. 2026-08-18 19:09 UTCEG score recompute
  15. 2026-08-18 13:48 UTCEPSS rescore
  16. 2026-08-17 14:48 UTCEG score recompute
  17. 2026-08-17 13:47 UTCEPSS rescore
  18. 2026-08-16 14:56 UTCEPSS rescore
  19. 2026-08-16 14:48 UTCEG score recompute
  20. 2026-08-15 14:48 UTCEG score recompute
  21. 2026-08-15 01:30 UTCEPSS rescore
  22. 2026-08-14 14:47 UTCEG score recompute
  23. 2026-08-13 22:00 UTCEPSS rescore
  24. 2026-08-12 14:47 UTCEG score recompute
  25. 2026-08-12 13:51 UTCEPSS rescore
  26. 2026-08-11 14:46 UTCEG score recompute
  27. 2026-08-11 00:00 UTCEPSS rescore
  28. 2026-08-09 14:46 UTCEG score recompute
  29. 2026-08-09 13:47 UTCEPSS rescore
  30. 2026-08-08 16:37 UTCEPSS rescore
  31. 2026-08-08 14:47 UTCEG score recompute
  32. 2026-08-06 14:47 UTCEG score recompute
  33. 2026-08-06 13:47 UTCEPSS rescore
  34. 2026-08-05 19:17 UTCEPSS rescore
  35. 2026-08-05 19:17 UTCEPSS rescore
  36. 2026-08-05 14:42 UTCEG score recompute
  37. 2026-08-04 15:10 UTCEPSS rescore
  38. 2026-08-04 14:43 UTCEG score recompute
  39. 2026-08-04 10:39 UTCEPSS rescore
  40. 2026-08-03 14:43 UTCEG score recompute
  41. 2026-08-03 10:36 UTCEPSS rescore
  42. 2026-08-02 14:43 UTCEG score recompute
  43. 2026-08-02 02:27 UTCEPSS rescore
  44. 2026-08-01 14:43 UTCEG score recompute
  45. 2026-08-01 04:16 UTCEPSS rescore
  46. 2026-07-31 14:42 UTCEG score recompute
  47. 2026-07-30 16:28 UTCEPSS rescore
  48. 2026-07-30 14:41 UTCEG score recompute
  49. 2026-07-30 01:30 UTCEPSS rescore
  50. 2026-07-30 01:30 UTCEPSS rescore
  51. 2026-07-29 14:39 UTCEG score recompute▼ 0.90
  52. 2026-07-29 14:39 UTCNVD updateCVSS v3 → 5.4
  53. 2026-07-28 16:31 UTCEG score recompute
  54. 2026-07-28 15:37 UTCEPSS rescore
  55. 2026-07-27 20:21 UTCEG score recompute
  56. 2026-07-27 20:00 UTCEG score recompute
  57. 2026-07-27 19:20 UTCEG score recompute▲ 6.30
  58. 2026-07-27 19:19 UTCMITRE cvelistV5CVSS v3 → 6.3 · CVSS v4 → 6.3
  59. 2026-07-23 03:22 UTCEG score recompute
  60. 2026-07-22 23:22 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-64647?
CVE-2026-64647 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-64647 disclosed?
CVE-2026-64647 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-64647 actively exploited?
CVE-2026-64647 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 71.6% of all scored CVEs.
What is the CVSS score of CVE-2026-64647?
CVE-2026-64647 has a CVSS v3 base score of 5.4 (NVD).
How do I remediate CVE-2026-64647?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64647, 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-64647

Explore →

Is Your Infrastructure Affected by CVE-2026-64647?

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

Start Free Scan →Browse All CVEs