How severe is GHSA-2p39-2jf3-fv2q?

No CVSS score has been assigned to GHSA-2p39-2jf3-fv2q yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-2p39-2jf3-fv2q?

GHSA-2p39-2jf3-fv2q affects the following packages: next-video (npm). Ecosystems affected: npm.

How do I fix GHSA-2p39-2jf3-fv2q?

Update next-video to 2.8.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2p39-2jf3-fv2q is resolved across your whole dependency graph.

How do I detect GHSA-2p39-2jf3-fv2q in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for next-video, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-2p39-2jf3-fv2q if there is no patch (or I can't update yet)?

Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Is GHSA-2p39-2jf3-fv2q actively exploited in the wild?

No public exploit code has been indexed for GHSA-2p39-2jf3-fv2q yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-2p39-2jf3-fv2q?

GHSA-2p39-2jf3-fv2q has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 34th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-2p39-2jf3-fv2q?

GHSA-2p39-2jf3-fv2q is classified as Path Traversal (CWE-22). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-2p39-2jf3-fv2q published, and has it been updated?

GHSA-2p39-2jf3-fv2q was published on August 20, 2026 and was last updated on August 20, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

GHSA-2p39-2jf3-fv2q — next-video

Fix: muxinc/next-video@73abf1d

GHSA-2p39-2jf3-fv2q is a Path Traversal vulnerability in next-video. A fix is available for next-video — see the affected versions and patch details below.

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

Also known asCVE-2026-54150

Published

Aug 20, 2026

Updated

Aug 20, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-2p39-2jf3-fv2q.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs34th percentile — riskier than 34% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

4other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

next-videonpm

46Kdownloads / week

Description

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

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`next-video`	all versions	2.8.1`npm install next-video@2.8.1`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for next-video, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update next-video to 2.8.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2p39-2jf3-fv2q is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Frequently Asked Questions

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

O3 Security · Impact-Aware SCA

Is GHSA-2p39-2jf3-fv2q in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works