# GHSA-673q-mjm6-r5xr: Next.js: Unauthenticated Remote Code Execution in `use cache` functions returning typed arrays


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 22 Oct 2026

## What is GHSA-673q-mjm6-r5xr?

GHSA-673q-mjm6-r5xr is a vulnerability in next, published on 22 Oct 2026. 

### Official 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.

## Which versions are affected by GHSA-673q-mjm6-r5xr?

2 open source packages ship an affected version, including next.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `next` | npm | From 16.0.0 | 16.4.1 |
| `next` | npm | From 16.0.0 | 16.4.1 |

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

Upgrade next to 16.4.1 or later.

## Is GHSA-673q-mjm6-r5xr being exploited?

There is no known exploitation of GHSA-673q-mjm6-r5xr in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-673q-mjm6-r5xr and fix it if it is affected.

What it is: GHSA-673q-mjm6-r5xr is a vulnerability in next, published on 22 Oct 2026. 
Exploitation: There is no known exploitation of GHSA-673q-mjm6-r5xr in the wild and no public exploit code.

Affected packages and fixed versions:
- next (npm): affected from 16.0.0; fixed in 16.4.1
- next (npm): affected from 16.0.0; fixed in 16.4.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-673q-mjm6-r5xr/ (Markdown: https://insights.sbomify.com/GHSA-673q-mjm6-r5xr/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-673q-mjm6-r5xr

---
From sbomify Insights: https://insights.sbomify.com/GHSA-673q-mjm6-r5xr/
Summaries are generated and may contain mistakes; the official description above is the record.