CVE-2026-54150: next-video Unauthenticated Arbitrary File Read Vulnerability

MODERATE
Advisory Identifier: GHSA-2p39-2jf3-fv2q
CWE-200
Published
Advisory Summary

CVE-2026-54150 is a MODERATE unauthenticated arbitrary file read vulnerability (CWE-200: Exposure of Sensitive Information to an Unauthorized Actor) affecting next-video libraries in the npm ecosystem. The issue involves unauthenticated arbitrary file read via /api/video request handler. Remediation is available by upgrading affected packages to version 2.8.1.

CVE-2026-54150 at a Glance

CVE Identifier CVE-2026-54150
GHSA Identifier GHSA-2p39-2jf3-fv2q
Severity MODERATE
CVSS v3.1 Base Score N/A
CWE Classification CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
Affected Product next-video
Package Ecosystem npm
Published Date
Last Updated

How to Fix CVE-2026-54150

To remediate this vulnerability, upgrade all affected next-video dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

next-video fixed: 2.8.1
npm install next-video@2.8.1
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls next-video

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2026-54150, inspect your project dependencies using npm:

npm ls next-video

Analyze the terminal output to locate any version of next-video in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.8.1), your application is affected.

Note: The npm ls next-video command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-200: Exposure of Sensitive Information to an Unauthorized Actor, where the product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. In next-video, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### 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. ### Patches 2.8.1 ### 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`

CVE-2026-54150 Affected next-video Versions

1 component(s)
Fixed Versions:
2.8.1
Product / Package Ecosystem Affected Versions Fixed Version
next-video
npm
< 2.8.1
2.8.1

References

Frequently Asked Questions

What is CVE-2026-54150?
CVE-2026-54150 is a security vulnerability in next-video involving Unauthenticated arbitrary file read via /api/video request handler under CWE-200: Exposure of Sensitive Information to an Unauthorized Actor.
Which next-video versions are affected?
Affected versions include releases prior to 2.8.1 across affected packages: next-video.
What version fixes CVE-2026-54150?
Upgrading to 2.8.1 (or the latest patched release for your respective branch) resolves the vulnerability.
Is next-video affected?
Yes, next-video is affected in releases prior to 2.8.1. Upgrade your dependency to 2.8.1 or later.
What CWE is associated with CVE-2026-54150?
CVE-2026-54150 is classified under CWE-200: Exposure of Sensitive Information to an Unauthorized Actor (The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.).
How can I check npm dependencies for CVE-2026-54150?
Run the dependency tree command: 'npm ls next-video'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-2p39-2jf3-fv2q",
  "modified" : "2026-08-20T18:35:11Z",
  "published" : "2026-08-20T18:35:11Z",
  "aliases" : [ "CVE-2026-54150" ],
  "summary" : "next-video: Unauthenticated arbitrary file read via /api/video request handler",
  "details" : "### Impact\n\nThe 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.\n\nThe 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.\n\nOn a typical Next.js deployment this exposes, at minimum:\n- The **Next.js Server Actions AES encryption key** (`.next/server/server-reference-manifest.json`)\n- The **Next.js Preview/Draft Mode keys** (`previewModeId`, `previewModeSigningKey`, `previewModeEncryptionKey`)\n- Internal build manifests, route registries, and absolute runtime paths\n- Application-specific asset metadata (e.g. Mux `uploadId`, `assetId`, `playbackId` values stored in `videos/*.json`)\n\nAny application that mounted `/api/video` following the documented one-liner is affected.\n\n### Patches\n\n2.8.1\n\n### Workarounds\n\nUntil a patched version is available, wrap the exported handler in your own route file and validate the `url` parameter before passing it through:\n\n- Reject any `url` value that does not begin with `https://`, or that does not match a known allowlist of trusted remote hosts.\n- 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.\n\n### References\n\n- `src/request-handler.ts` — the vulnerable GET handler\n- `src/assets.ts` — `getAssetPath()`, where the local-vs-remote branching occurs\n- `src/utils/utils.ts` — `isRemote()`, the sole guard between the two branches\n- `src/config.ts` — `loadAsset()`, which performs the unconstrained `fs.readFile`",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "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"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "next-video"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "2.8.1"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 2.8.0"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/muxinc/next-video/security/advisories/GHSA-2p39-2jf3-fv2q"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/muxinc/next-video/commit/73abf1d534c2ac48db546ecfed0e89cbaf124f6f"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/muxinc/next-video"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/muxinc/next-video/releases/tag/v2.8.1"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-200" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-08-20T18:35:11Z",
    "nvd_published_at" : null
  }
}