How severe is GHSA-6gpp-xcg3-4w24?

No CVSS score has been assigned to GHSA-6gpp-xcg3-4w24 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-6gpp-xcg3-4w24?

GHSA-6gpp-xcg3-4w24 affects the following packages: next (npm). Ecosystems affected: npm.

How do I fix GHSA-6gpp-xcg3-4w24?

Update next to 16.2.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6gpp-xcg3-4w24 is resolved across your whole dependency graph.

How do I detect GHSA-6gpp-xcg3-4w24 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-6gpp-xcg3-4w24 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-6gpp-xcg3-4w24 actively exploited in the wild?

No public exploit code has been indexed for GHSA-6gpp-xcg3-4w24 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-6gpp-xcg3-4w24?

GHSA-6gpp-xcg3-4w24 has an EPSS (Exploit Prediction Scoring System) score of 0.6%, placing it in the 50th 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-6gpp-xcg3-4w24?

GHSA-6gpp-xcg3-4w24 is classified as CWE-285 (CWE-285). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-6gpp-xcg3-4w24 published, and has it been updated?

GHSA-6gpp-xcg3-4w24 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: Middleware / Proxy bypass in App Router applications using Turbopack and single localeGHSA-6gpp-xcg3-4w24

Fix: vercel/next.js#96014

GHSA-6gpp-xcg3-4w24 is a CWE-285 vulnerability in next. A fix is available for next — see the affected versions and patch details below.

Also known asCVE-2026-64642

Published

Jul 22, 2026

Updated

Sep 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 23, 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-6gpp-xcg3-4w24.

EPSS Exploitation Probability

via FIRST.org ↗

0.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs50th percentile — riskier than 50% of all scored CVEsHighest risk

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

Real-World Exposure

1 pkg 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

Crafted requests targeting Next.js applications using App Router built with Turbopack and a single entry in config.i18n.locales can bypass middleware/proxy based authentication.

Workarounds

If you cannot upgrade immediately, enforce authorization in the page's server-side data path instead of relying solely on middleware.

Affected Packages

1 total 1 fixed

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

Affected Products

1 product · 1 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 16.2.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6gpp-xcg3-4w24 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 Crafted requests targeting Next.js applications using App Router built with Turbopack and a **single** entry in `config.i18n.locales` can bypass middleware/proxy based authentication. ## Workarounds If you cannot upgrade immediately, enforce authorization in the page's server-side data path instead of relying solely on middleware.

O3 Security · Impact-Aware SCA

Is GHSA-6gpp-xcg3-4w24 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works