# Denial of Service Vulnerability in React Server Components

Advisory record · `GHSA-7gmr-mq3h-m5h9`

- **Identifiers:** `GHSA-7gmr-mq3h-m5h9` · `CVE-2025-67779`
- **State:** Confirmed
- **Severity:** CVSS 7.5 High
- **Critical:** Yes: CVSS 7+ and EPSS
- **Weakness (CWE):** [CWE-400](https://cwe.mitre.org/data/definitions/400.html) · [CWE-502](https://cwe.mitre.org/data/definitions/502.html)
- **Tags:** [Denial of service](https://agentprime.io/advisories/tag/dos.md) · [Insecure deserialization](https://agentprime.io/advisories/tag/deserialization.md)
- **Published:** 12 Dec 2025
- **Updated:** 12 Dec 2025
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 12 Dec 2025, 16:32 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Critical

Critical, because:

- CVSS score 7.5 (7.0 or more) and EPSS 0.15 (0.1 or more): a high score and a real chance of exploitation in the next 30 days.

How we decide what’s critical: <https://agentprime.io/advisories/critical.md>

## Affected packages

- `react-server-dom-parcel` (npm): affected `>=19.0.2, <19.0.3 || >=19.1.3, <19.1.4 || >=19.2.2, <19.2.3`; fixed in `19.0.3`, `19.1.4`, `19.2.3`
- `react-server-dom-turbopack` (npm): affected `>=19.0.2, <19.0.3 || >=19.1.3, <19.1.4 || >=19.2.2, <19.2.3`; fixed in `19.0.3`, `19.1.4`, `19.2.3`
- `react-server-dom-webpack` (npm): affected `>=19.0.2, <19.0.3 || >=19.1.3, <19.1.4 || >=19.2.2, <19.2.3`; fixed in `19.0.3`, `19.1.4`, `19.2.3`

## 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 CNA (Meta)

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

## Timeline

- 12 Dec 2025, 00:17 UTC: [Published by the maintainers as a GitHub repository advisory](https://github.com/react/react/security/advisories/GHSA-7gmr-mq3h-m5h9)

## Sources

- [GitHub Advisory Database: GHSA-7gmr-mq3h-m5h9](https://github.com/advisories/GHSA-7gmr-mq3h-m5h9)
- [OSV: GHSA-7gmr-mq3h-m5h9](https://osv.dev/vulnerability/GHSA-7gmr-mq3h-m5h9)
- <https://github.com/facebook/react/security/advisories/GHSA-2m3v-v2m8-q956>
- <https://github.com/facebook/react/security/advisories/GHSA-7gmr-mq3h-m5h9>
- <https://nvd.nist.gov/vuln/detail/CVE-2025-67779>
- <https://github.com/facebook/react>
- <https://react.dev/blog/2025/12/11/denial-of-service-and-source-code-exposure-in-react-server-components>

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-7gmr-mq3h-m5h9>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-7gmr-mq3h-m5h9/>. Everything for agents: <https://agentprime.io/llms.txt>.