CVE-2026-54150
Received Received - Intake

Path Traversal in Next.js next-video Library

Vulnerability report for CVE-2026-54150, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-09-14

Last updated on: 2026-09-14

Assigner: GitHub, Inc.

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-14
Last Modified
2026-09-14
Generated
2026-09-14
AI Q&A
2026-09-14
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 2 associated CPEs
Vendor Product Version / Range
next-video next-video 2.8.1
muxinc next-video to 2.8.1 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-22 The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability affects the next-video library for Next.js. It allows unauthenticated attackers to read arbitrary JSON files from the filesystem by exploiting an improperly validated 'url' query parameter in the /api/video endpoint. The handler treats non-HTTP(S) values as local paths, enabling directory traversal to access sensitive files like encryption keys or build manifests.

Detection Guidance

Check if your application exposes the /api/video endpoint. Test if the url parameter accepts local file paths and attempts to read JSON files outside the intended directory. Look for unauthorized access to sensitive files like Next.js encryption keys or build manifests.

Impact Analysis

Attackers could read sensitive files on your server, including Next.js server-action encryption material, preview-mode keys, build manifests, route metadata, absolute paths, and video asset identifiers. This could lead to data breaches or further exploitation of your application.

Compliance Impact

This vulnerability could expose sensitive data such as encryption keys, build manifests, and application metadata, which may include personally identifiable information (PII) or protected health information (PHI). Unauthorized access to such data could lead to violations of GDPR, HIPAA, or other privacy regulations depending on the data processed by the application.

Mitigation Strategies
  • Upgrade next-video to version 2.8.1 or later immediately to patch the vulnerability.
  • If upgrading is not possible, remove or disable the /api/video route if it is not required for your application.
  • Validate the url parameter in the /api/video endpoint to ensure it only accepts remote URLs with http:// or https:// prefixes.
  • Monitor file access logs for suspicious attempts to read JSON files outside the intended video asset directory.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-54150. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart