Path Traversal in next-video (CVE-2026-54150)
Summary
Path traversal in next-video (CVE-2026-54150). Risk of unauthorized operations or information disclosure. Exploitable via GET. Mitigation: upgrade to 2.8.1 or later.
Original description
The description as published by the source.
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,playbackIdvalues stored invideos/*.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:…
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-54150 has been found in next-video.
Attackers can target a specific entry point like GET over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade next-video to 2.8.1 or later.
If unsure, ask your IT team or search "next-video CVE-2026-54150" on the vendor's site.
CVE-2026-54150 (next-video) — CWE-22
Attack surface: GET / url / fs.readFile / previewModeId
Patched: 2.8.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Path traversal (CWE-22) exists in next-video. Attackers reach the vulnerable code path via GET.
Check the vendor advisory for the affected versions of next-video. Attack surface: GET / url / fs.readFile / previewModeId.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 2.8.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'next-video' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'next-video' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
next-videoを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade next-video to 2.8.1ステージング環境で 2.8.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com