# GHSA-w37m-7fhw-fmv9: Next Server Actions Source Code Exposure > Attackers can send malicious HTTP requests to App Router endpoints to retrieve compiled source code of Server Functions, potentially exposing business logic. - **Severity:** Not scored - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 11 Dec 2025 ## What is GHSA-w37m-7fhw-fmv9? GHSA-w37m-7fhw-fmv9 is a vulnerability in next, published on 11 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description A vulnerability affects certain React packages for versions 19.0.0, 19.0.1, 19.1.0, 19.1.1, 19.1.2, 19.2.0, and 19.2.1 and frameworks that use the affected packages, including Next.js 15.x and 16.x using the App Router. The issue is tracked upstream as [CVE-2025-55183](https://www.cve.org/CVERecord?id=CVE-2025-55183). A malicious HTTP request can be crafted and sent to any App Router endpoint that can return the compiled source code of [Server Functions](https://react.dev/reference/rsc/server-functions). This could reveal business logic, but would not expose secrets unless they were hardcoded directly into [Server Function](https://react.dev/reference/rsc/server-functions) code. ## Which versions are affected by GHSA-w37m-7fhw-fmv9? 18 open source packages ship an affected version, including next. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `next` | npm | From 15.0.0-canary.0 | 15.0.6 | | `next` | npm | From 15.0.0-canary.0 | 15.0.6 | | `next` | npm | From 15.1.1-canary.0 | 15.1.10 | | `next` | npm | From 15.1.1-canary.0 | 15.1.10 | | `next` | npm | From 15.2.0-canary.0 | 15.2.7 | | `next` | npm | From 15.2.0-canary.0 | 15.2.7 | | `next` | npm | From 15.3.0-canary.0 | 15.3.7 | | `next` | npm | From 15.3.0-canary.0 | 15.3.7 | | `next` | npm | From 15.4.0-canary.0 | 15.4.9 | | `next` | npm | From 15.4.0-canary.0 | 15.4.9 | | `next` | npm | From 15.5.1-canary.0 | 15.5.8 | | `next` | npm | From 15.5.1-canary.0 | 15.5.8 | | `next` | npm | From 15.6.0-canary.0 | 15.6.0-canary.59 | | `next` | npm | From 15.6.0-canary.0 | 15.6.0-canary.59 | | `next` | npm | From 16.0.0-beta.0 | 16.0.9 | | `next` | npm | From 16.0.0-beta.0 | 16.0.9 | | `next` | npm | From 16.1.0-canary.0 | 16.1.0-canary.17 | | `next` | npm | From 16.1.0-canary.0 | 16.1.0-canary.17 | ## How do I fix GHSA-w37m-7fhw-fmv9? Upgrade next to a fixed version for your release line: 15.0.6, 15.1.10, 15.2.7 or 15.3.7. ## Is GHSA-w37m-7fhw-fmv9 being exploited? There is no known exploitation of GHSA-w37m-7fhw-fmv9 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for GHSA-w37m-7fhw-fmv9 and fix it if it is affected. What it is: GHSA-w37m-7fhw-fmv9 is a vulnerability in next, published on 11 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of GHSA-w37m-7fhw-fmv9 in the wild and no public exploit code. Affected packages and fixed versions: - next (npm): affected from 15.0.0-canary.0; fixed in 15.0.6 - next (npm): affected from 15.0.0-canary.0; fixed in 15.0.6 - next (npm): affected from 15.1.1-canary.0; fixed in 15.1.10 - next (npm): affected from 15.1.1-canary.0; fixed in 15.1.10 - next (npm): affected from 15.2.0-canary.0; fixed in 15.2.7 - next (npm): affected from 15.2.0-canary.0; fixed in 15.2.7 - next (npm): affected from 15.3.0-canary.0; fixed in 15.3.7 - next (npm): affected from 15.3.0-canary.0; fixed in 15.3.7 - next (npm): affected from 15.4.0-canary.0; fixed in 15.4.9 - next (npm): affected from 15.4.0-canary.0; fixed in 15.4.9 - next (npm): affected from 15.5.1-canary.0; fixed in 15.5.8 - next (npm): affected from 15.5.1-canary.0; fixed in 15.5.8 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-w37m-7fhw-fmv9/ (Markdown: https://insights.sbomify.com/GHSA-w37m-7fhw-fmv9/index.md) ``` ## Sources - OSV: https://osv.dev/vulnerability/GHSA-w37m-7fhw-fmv9 --- From sbomify Insights: https://insights.sbomify.com/GHSA-w37m-7fhw-fmv9/ Summaries are generated and may contain mistakes; the official description above is the record.