How severe is GHSA-673q-mjm6-r5xr?

No CVSS score has been assigned to GHSA-673q-mjm6-r5xr yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-673q-mjm6-r5xr?

GHSA-673q-mjm6-r5xr affects the following packages: next (npm). Ecosystems affected: npm.

How do I fix GHSA-673q-mjm6-r5xr?

Update next to 16.4.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-673q-mjm6-r5xr is resolved across your whole dependency graph.

How do I detect GHSA-673q-mjm6-r5xr 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-673q-mjm6-r5xr 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-673q-mjm6-r5xr actively exploited in the wild?

No public exploit code has been indexed for GHSA-673q-mjm6-r5xr 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.

When was GHSA-673q-mjm6-r5xr published, and has it been updated?

GHSA-673q-mjm6-r5xr was published on October 22, 2026 and was last updated on October 22, 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: Unauthenticated Remote Code Execution in `use cache` functions returning typed arraysGHSA-673q-mjm6-r5xr

Fix: vercel/next.js@a4cea6a

GHSA-673q-mjm6-r5xr is a remote code execution vulnerability in next. A fix is available for next — see the affected versions and patch details below.

Published

Oct 22, 2026

Updated

Oct 22, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 22, 2026 · OSV.dev, 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

A vulnerability in applications using App router with Cache Component can lead to remote code execution. The application needs to have a use cache function that returns multiple typed arrays.

Workaround

There is no known workaround for affected applications with such use cache functions. You should upgrade immediately even if your application does not have similar functions.

Affected Packages

1 total 1 fixed

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

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.4.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-673q-mjm6-r5xr 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 vulnerability in applications using App router with Cache Component can lead to remote code execution. The application needs to have a `use cache` function that returns multiple typed arrays. ## Workaround There is no known workaround for affected applications with such `use cache` functions. You should upgrade immediately even if your application does not have similar functions.

O3 Security · Impact-Aware SCA

Is GHSA-673q-mjm6-r5xr in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works