MediumGHSA-w37m-7fhw-fmv9

Next Server Actions Source Code Exposure

Published 11 Dec 2025 · Updated 10 Sept 2026

Affected packages

nextnpm
Affected
>=15.0.0-canary.0 <15.0.6
Fixed in
15.0.6
Update to the fixed version for your release line, for example:npm install next@15.0.6
nextnpm
Affected
>=15.1.1-canary.0 <15.1.10
Fixed in
15.1.10
Update to the fixed version for your release line, for example:npm install next@15.1.10
nextnpm
Affected
>=15.2.0-canary.0 <15.2.7
Fixed in
15.2.7
Update to the fixed version for your release line, for example:npm install next@15.2.7
nextnpm
Affected
>=15.3.0-canary.0 <15.3.7
Fixed in
15.3.7
Update to the fixed version for your release line, for example:npm install next@15.3.7
nextnpm
Affected
>=15.4.0-canary.0 <15.4.9
Fixed in
15.4.9
Update to the fixed version for your release line, for example:npm install next@15.4.9
nextnpm
Affected
>=15.5.1-canary.0 <15.5.8
Fixed in
15.5.8
Update to the fixed version for your release line, for example:npm install next@15.5.8
nextnpm
Affected
>=15.6.0-canary.0 <15.6.0-canary.59
Fixed in
15.6.0-canary.59
Update to the fixed version for your release line, for example:npm install next@15.6.0-canary.59
nextnpm
Affected
>=16.0.0-beta.0 <16.0.9
Fixed in
16.0.9
Update to the fixed version for your release line, for example:npm install next@16.0.9
nextnpm
Affected
>=16.1.0-canary.0 <16.1.0-canary.17
Fixed in
16.1.0-canary.17
Update to the fixed version for your release line, for example:npm install next@16.1.0-canary.17

Details

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.

A malicious HTTP request can be crafted and sent to any App Router endpoint that can return the compiled source code of Server Functions. This could reveal business logic, but would not expose secrets unless they were hardcoded directly into Server Function code.

Is GHSA-w37m-7fhw-fmv9 in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected next, and gives you the command that fixes it.

Scan a project free, no signupOr connect GitHub to scan every repo

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.