How severe is GHSA-4633-3j49-mh5q?

No CVSS score has been assigned to GHSA-4633-3j49-mh5q yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-4633-3j49-mh5q?

GHSA-4633-3j49-mh5q affects the following packages: next (npm), next (npm). Ecosystems affected: npm.

How do I fix GHSA-4633-3j49-mh5q?

Update next to 15.5.21 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4633-3j49-mh5q is resolved across your whole dependency graph.

How do I detect GHSA-4633-3j49-mh5q in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for next, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-4633-3j49-mh5q if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-4633-3j49-mh5q actively exploited in the wild?

No public exploit code has been indexed for GHSA-4633-3j49-mh5q yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-4633-3j49-mh5q?

GHSA-4633-3j49-mh5q has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 23th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-4633-3j49-mh5q?

GHSA-4633-3j49-mh5q is classified as CWE-116 (CWE-116). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-4633-3j49-mh5q published, and has it been updated?

GHSA-4633-3j49-mh5q was published on July 22, 2026 and was last updated on September 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

Next.js: Cache confusion of response bodies for requests with bodies containing invalid UTF-8 byte sequencesGHSA-4633-3j49-mh5q

Fix: vercel/next.js#96008

GHSA-4633-3j49-mh5q is a CWE-116 vulnerability in next. A fix is available for next — see the affected versions and patch details below.

Also known asCVE-2026-64647

Published

Jul 22, 2026

Updated

Sep 10, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Oct 24, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-4633-3j49-mh5q.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs23th percentile — riskier than 23% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

2 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

61Kother npm packages depend on this — each one inherits the vulnerability until it's patched upstream

nextnpm

44.6Mdownloads / week

Description

Impact

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.

Workarounds

If you cannot upgrade, consider only making fetch requests with UTF-8 bodies (default in Next.js). Applications using Pages Router are not vulnerable.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`next`	≥ 13.0.0&&< 15.5.21	15.5.21`npm install next@15.5.21`
📦npm	`next`	≥ 16.0.0&&< 16.2.11	16.2.11`npm install next@16.2.11`

Affected Products

1 product · 2 configurations

Application

next.jsvercel

≥ 16.0.0 && < 16.2.11

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for next, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update next to 15.5.21 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4633-3j49-mh5q is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

## Impact 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. ## Workarounds If you cannot upgrade, consider only making fetch requests with UTF-8 bodies (default

O3 Security · Impact-Aware SCA

Is GHSA-4633-3j49-mh5q in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works