What is CVE-2026-54150?

CVE-2026-54150 is a medium-severity security vulnerability in next-video (npm), affecting versions <= 2.8.0. It is fixed in 2.8.1.

Which versions of next-video are affected by CVE-2026-54150?

next-video (npm) versions <= 2.8.0 is affected.

Is there a fix for CVE-2026-54150?

Yes. CVE-2026-54150 is fixed in 2.8.1. Upgrade to this version or later.

Is CVE-2026-54150 exploitable, and should I be worried?

Whether CVE-2026-54150 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2026-54150 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2026-54150?

Upgrade next-video to 2.8.1 or later.

CVE-2026-54150 in next-video

Q: Which versions of next-video are affected by CVE-2026-54150?

next-video (npm) versions <= 2.8.0 is affected.

Q: Is there a fix for CVE-2026-54150?

Yes. CVE-2026-54150 is fixed in 2.8.1. Upgrade to this version or later.

Q: Is CVE-2026-54150 exploitable, and should I be worried?

Whether CVE-2026-54150 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2026-54150 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2026-54150?

Upgrade next-video to 2.8.1 or later.

Summary

next-video: Unauthenticated arbitrary file read via /api/video request handler

Workarounds

Until a patched version is available, wrap the exported handler in your own route file and validate the url parameter before passing it through:

Reject any url value that does not begin with https://, or that does not match a known allowlist of trusted remote hosts.
Alternatively, remove the /api/video route entirely if your application only uses build-time import of local video files and does not use <Video src="https://..."> with string URLs at runtime.

References

src/request-handler.ts, the vulnerable GET handler
src/assets.ts, getAssetPath(), where the local-vs-remote branching occurs
src/utils/utils.ts, isRemote(), the sole guard between the two branches
src/config.ts, loadAsset(), which performs the unconstrained fs.readFile

Impact

The HTTP route handler exported by next-video/request-handler, which the README instructs consumers to mount at /api/video, allows an unauthenticated remote attacker to read arbitrary .json files from the production filesystem of any application following the documented setup.

The handler's GET endpoint accepts a url query parameter and uses it to locate and serve a JSON asset descriptor from disk. The only guard between "remote URL" and "local file path" is a regex check for ^https?://. Any value that does not match that prefix is treated as a local path, .json is appended, and the file is read with fs.readFile and returned in the HTTP response, with no authentication, no path canonicalization, and no traversal guard.

On a typical Next.js deployment this exposes, at minimum:

The Next.js Server Actions AES encryption key (.next/server/server-reference-manifest.json)
The Next.js Preview/Draft Mode keys (previewModeId, previewModeSigningKey, previewModeEncryptionKey)
Internal build manifests, route registries, and absolute runtime paths
Application-specific asset metadata (e.g. Mux uploadId, assetId, playbackId values stored in videos/*.json)

Any application that mounted /api/video following the documented one-liner is affected.

Affected versions

next-video (<= 2.8.0)

Security releases

next-video → 2.8.1 (npm)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

2.8.1

Frequently Asked Questions

What is CVE-2026-54150? CVE-2026-54150 is a medium-severity security vulnerability in next-video (npm), affecting versions <= 2.8.0. It is fixed in 2.8.1.
Which versions of next-video are affected by CVE-2026-54150? next-video (npm) versions <= 2.8.0 is affected.
Is there a fix for CVE-2026-54150? Yes. CVE-2026-54150 is fixed in 2.8.1. Upgrade to this version or later.
Is CVE-2026-54150 exploitable, and should I be worried? Whether CVE-2026-54150 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2026-54150 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2026-54150? Upgrade next-video to 2.8.1 or later.