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

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 Sep 2026
- **Updated:** 14 Sep 2026
- **Also known as:** GHSA-2p39-2jf3-fv2q

## 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 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-54150?

2 open source packages ship an affected version, including next-video.


| Package | Ecosystem | 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.

## Is CVE-2026-54150 being exploited?

There is no known exploitation of CVE-2026-54150 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-54150 and fix it if it is affected.

What it is: 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.
Exploitation: There is no known exploitation of CVE-2026-54150 in the wild and no public exploit code.

Affected packages and fixed versions:
- next-video (npm): affected all versions; fixed in 2.8.1
- next-video (npm): affected all versions; fixed in 2.8.1

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/CVE-2026-54150/ (Markdown: https://insights.sbomify.com/CVE-2026-54150/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-54150
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-54150
- OSV: https://osv.dev/vulnerability/CVE-2026-54150

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-54150/
Summaries are generated and may contain mistakes; the official description above is the record.