{"answers":{"affected":"2 open source packages ship an affected version, including next-video.","exploited":"There is no known exploitation of CVE-2026-54150 in the wild and no public exploit code.","fix":"Upgrade next-video to 2.8.1 or later.","what":"CVE-2026-54150 is a medium-severity path traversal vulnerability in muxinc next-video, published on 14 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-54150 and fix it if it is affected.\n\nWhat it is: CVE-2026-54150 is a medium-severity path traversal vulnerability in muxinc next-video, published on 14 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-54150 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- next-video (npm): affected all versions; fixed in 2.8.1\n- next-video (npm): affected all versions; fixed in 2.8.1\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-54150/ (Markdown: https://insights.sbomify.com/CVE-2026-54150/index.md)","id":"CVE-2026-54150","markdown":"https://insights.sbomify.com/CVE-2026-54150/index.md","name":"CVE-2026-54150","record":{"aliases":["GHSA-2p39-2jf3-fv2q"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Next.js video library","requires_auth":"none","summary":"Remote attackers can read arbitrary JSON files from the server via path traversal in the video request handler, exposing sensitive application data.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"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.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"next-video: Unauthenticated arbitrary file read via /api/video request handler","id":"CVE-2026-54150","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":2,"n_references":3,"next":{"headline":"node-opcua: Missing nonce verification in UserNameIdentityToken authentication","id":"CVE-2026-54155"},"packages":[{"ecosystem":"npm","fixed":["2.8.1"],"introduced":["0"],"last_affected":[],"package":"next-video","purl":null,"source":"GHSA-2p39-2jf3-fv2q"},{"ecosystem":"npm","fixed":["2.8.1"],"introduced":["0"],"last_affected":[],"package":"next-video","purl":"pkg:npm/next-video","source":"GHSA-2p39-2jf3-fv2q"}],"prev":{"headline":"MaxKB MCP tool import validation bypass allows post-authentication remote code execution","id":"CVE-2026-54149"},"products":["next-video"],"published":"2026-09-14","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-14","vendors":["muxinc"]},"summary":"Remote attackers can read arbitrary JSON files from the server via path traversal in the video request handler, exposing sensitive application data.","url":"https://insights.sbomify.com/CVE-2026-54150/"}