# Next.js HTTP request deserialization can lead to DoS when using insecure React Server Components

Advisory record · `GHSA-h25m-26qc-wcjf`

- **Identifiers:** `GHSA-h25m-26qc-wcjf` · `CVE-2026-23864`
- **State:** Confirmed
- **Severity:** CVSS 7.5 High
- **Critical:** No
- **Weakness (CWE):** [CWE-400](https://cwe.mitre.org/data/definitions/400.html) · [CWE-502](https://cwe.mitre.org/data/definitions/502.html) · [CWE-1284](https://cwe.mitre.org/data/definitions/1284.html)
- **Tags:** [Denial of service](https://agentprime.io/advisories/tag/dos.md) · [Insecure deserialization](https://agentprime.io/advisories/tag/deserialization.md) · [CWE-1284](https://agentprime.io/advisories/tag/cwe-1284.md)
- **Published:** 28 Jan 2026
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 28 Jan 2026, 15:38 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `next` (npm): affected `>=13.0.0, <15.0.8 || >=15.1.1-canary.0, <15.1.12 || >=15.2.0-canary.0, <15.2.9 || >=15.3.0-canary.0, <15.3.9 || >=15.4.0-canary.0, <15.4.11 || >=15.5.1-canary.0, <15.5.10 || >=15.6.0-canary.0, <15.6.0-canary.61 || >=16.0.0-beta.0, <16.0.11 || >=16.1.0-canary.0, <16.1.5`; fixed in `15.0.8`, `15.1.12`, `15.2.9`, `15.3.9`, `15.4.11`, `15.5.10`, `15.6.0-canary.61`, `16.0.11`, `16.1.5`

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 7.5 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** 0.026, the 85th percentile, on 12 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 26 Jan 2026, 19:17 UTC: [Published by the maintainers as a GitHub repository advisory](https://github.com/vercel/next.js/security/advisories/GHSA-h25m-26qc-wcjf)

## Sources

- [GitHub Advisory Database: GHSA-h25m-26qc-wcjf](https://github.com/advisories/GHSA-h25m-26qc-wcjf)
- [OSV: GHSA-h25m-26qc-wcjf](https://osv.dev/vulnerability/GHSA-h25m-26qc-wcjf)
- <https://github.com/facebook/react/security/advisories/GHSA-83fc-fqcc-2hmg>
- <https://github.com/vercel/next.js/security/advisories/GHSA-h25m-26qc-wcjf>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-23864>
- <https://github.com/vercel/next.js>
- <https://vercel.com/changelog/summary-of-cve-2026-23864>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-h25m-26qc-wcjf>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-h25m-26qc-wcjf/>. Everything for agents: <https://agentprime.io/llms.txt>.