CVE-2026-54150 next-video: Unauthenticated arbitrary file read via /api/video request handler
Remote attackers can read arbitrary JSON files from the server via path traversal in the video request handler, exposing sensitive application data.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-54150?
CVE-2026-54150 is a medium-severity path traversal vulnerability in muxinc next-video, published on 14 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
next-video is a library for adding video to Next.js applications. Prior to 2.8.1, the GET endpoint exported by next-video/request-handler and commonly mounted at /api/video accepts an unauthenticated url query parameter, while src/utils/utils.ts isRemote() treats any value without an HTTP or HTTPS prefix as a local path. src/request-handler.ts passes that value through src/assets.ts getAssetPath() to src/config.ts loadAsset(), which appends a JSON suffix and uses fs.readFile without canonicalizing the path or verifying that it remains inside the configured video folder. A remote attacker can therefore escape the intended asset directory and read JSON files accessible to the application process, including Next.js server-action encryption material, preview-mode keys, build manifests, route metadata, absolute paths, and application video asset identifiers. Applications that do not expose the runtime request handler are not affected through this route. This issue is fixed in version 2.8.1.
Weakness: CWE-22
Which versions are affected by CVE-2026-54150?
2 open source packages ship an affected version, including next-video.
| Package | Affected | Fixed in |
|---|---|---|
next-video npm | All versions | 2.8.1 |
next-video npm | All versions | 2.8.1 |
How do I fix CVE-2026-54150?
Upgrade next-video to 2.8.1 or later.
Upgrade, and resolve every user-supplied path against an allowed base folder before opening it. More about Path traversal.
Is CVE-2026-54150 being exploited?
There is no known exploitation of CVE-2026-54150 in the wild and no public exploit code.
Sources
Also known as GHSA-2p39-2jf3-fv2q.