# Next.js Improper Middleware Redirect Handling Leads to SSRF

Advisory record · `GHSA-4342-x723-ch2f`

- **Identifiers:** `GHSA-4342-x723-ch2f` · `CVE-2025-57822`
- **State:** Confirmed
- **Severity:** CVSS 6.5 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-918](https://cwe.mitre.org/data/definitions/918.html)
- **Tags:** [Server-side request forgery (SSRF)](https://agentprime.io/advisories/tag/ssrf.md)
- **Published:** 29 Aug 2025
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 29 Aug 2025, 21:33 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `next` (npm): affected `>=0.9.9, <14.2.32 || >=15.0.0-canary.0, <15.4.7`; fixed in `14.2.32`, `15.4.7`

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

- 6.5 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N`, from CNA (GitHub_M)

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

## Timeline

- 29 Aug 2025, 21:23 UTC: [Published by the maintainers as a GitHub repository advisory](https://github.com/vercel/next.js/security/advisories/GHSA-4342-x723-ch2f)

## Sources

- [GitHub Advisory Database: GHSA-4342-x723-ch2f](https://github.com/advisories/GHSA-4342-x723-ch2f)
- [OSV: GHSA-4342-x723-ch2f](https://osv.dev/vulnerability/GHSA-4342-x723-ch2f)
- <https://github.com/vercel/next.js/security/advisories/GHSA-4342-x723-ch2f>
- <https://nvd.nist.gov/vuln/detail/CVE-2025-57822>
- <https://github.com/vercel/next.js/commit/9c9aaed5bb9338ef31b0517ccf0ab4414f2093d8>
- <https://github.com/vercel/next.js>
- <https://vercel.com/changelog/cve-2025-57822>

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

---

The web page: <https://agentprime.io/advisories/GHSA-4342-x723-ch2f/>. Everything for agents: <https://agentprime.io/llms.txt>.
