How severe is GHSA-68g3-v927-f742?

No CVSS score has been assigned to GHSA-68g3-v927-f742 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-68g3-v927-f742?

GHSA-68g3-v927-f742 affects the following packages: next (npm), next (npm). Ecosystems affected: npm.

How do I fix GHSA-68g3-v927-f742?

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

How do I detect GHSA-68g3-v927-f742 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-68g3-v927-f742 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-68g3-v927-f742 actively exploited in the wild?

No public exploit code has been indexed for GHSA-68g3-v927-f742 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-68g3-v927-f742?

GHSA-68g3-v927-f742 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 25th 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-68g3-v927-f742?

GHSA-68g3-v927-f742 is classified as CWE-524 (CWE-524). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-68g3-v927-f742 published, and has it been updated?

GHSA-68g3-v927-f742 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 bodiesGHSA-68g3-v927-f742

Fix: vercel/next.js@062f667

GHSA-68g3-v927-f742 is a CWE-524 vulnerability in next. A fix is available for next — see the affected versions and patch details below.

Also known asCVE-2026-64648

Published

Jul 22, 2026

Updated

Sep 10, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Oct 12, 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-68g3-v927-f742.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs25th percentile — riskier than 25% 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

67.7Mdownloads / week

Description

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.

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-68g3-v927-f742 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.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

This Important information disclosure flaw in Next.js arises from a server-side fetch cache confusion, potentially leaking confidential data from POST response bodies to unauthorized requests. The vulnerability is triggered by specific unsafe fetch patterns where the request object's initialization differs from the…

Product	Fixed in	Advisory
Streams for Apache Kafka 3.2.1	`next`	RHSA-2026:54435

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 only applies to `fetch` calls with a request that has a different init than the one passed to `fetch`. Safe: `fetch(new Request(init), init)` Unsafe: `fetch(new Request(init), aDifferentInit)` ## Workarounds No workaround exists besides upgrading. Applications using Pages Router are not vulnerable.

O3 Security · Impact-Aware SCA

Is GHSA-68g3-v927-f742 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works