Which versions of OpenCode Studio are affected by CVE-2026-69110?

OpenCode Studio versions before 2.4.4 contain a critical vulnerability allowing any remote attacker to steal and delete other users' video and audio projects without authentication.. A patch is available.

Is there a public PoC exploit available for CVE-2026-69110?

Yes, a public proof-of-concept exploit is available for CVE-2026-69110. Prioritise patching immediately. EPSS: 0.5%.

How to fix or mitigate CVE-2026-69110?

Within 24 hours, identify all systems running OpenCode Studio and confirm their current versions; check access logs on affected endpoints (/api/tmp, /api/music, /api/short-video) for signs of exploitation. Within 7 days, upgrade all affected instances to OpenCode Studio 2.4.4 or later and validate the upgrade across production systems. Within 30 days, conduct a forensic review of logs from the vulnerability window to detect unauthorized access, complete incident documentation, and implement a process to apply critical patches within 72 hours of release.

OpenCode Studio CVE-2026-69110

Q: What is the CVSS score of CVE-2026-69110?

CVE-2026-69110 has a CVSS 4.0 base score of 9.3 (Critical). CVSS vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. EPSS exploitation probability: 0.5%.

EUVD-2026-52743 CRITICAL

Path Traversal (CWE-22)

2026-08-04 VulnCheck

GHSA-7fr9-h24p-27wp

Authentication Bypass Path Traversal Opencode Studio

9.3

CVSS 4.0 · Vendor: VulnCheck

Severity by source

Vendor (VulnCheck) PRIMARY

9.3 CRITICAL

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

vuln.today AI

9.1 CRITICAL

Remote, no auth or interaction, low complexity (PR:N/UI:N/AC:L); high confidentiality from cross-user file read and high integrity from arbitrary video deletion, no direct availability metric claimed.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (VulnCheck).

CVSS VectorVendor: VulnCheck

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Lifecycle Timeline

Source Code Evidence Fetched

Aug 04, 2026 - 16:05 vuln.today

Analysis Generated

Aug 04, 2026 - 16:05 vuln.today

CVE Published

Aug 04, 2026 - 15:30 cve.org

CRITICAL 9.3

DescriptionCVE.org

OpenCode Studio before 2.4.4 contains a missing authentication vulnerability that allows unauthenticated remote attackers to read arbitrary files within the temp and static/music directories by directly accessing the GET /api/tmp/:tmpFile and GET /api/music/:fileName endpoints. Attackers can retrieve intermediate audio, video artifacts, and subtitles belonging to other users' jobs, and additionally delete any video by ID through the unauthenticated DELETE /api/short-video/:videoId endpoint.

AnalysisAI

Unauthenticated arbitrary file read in OpenCode Studio before 2.4.4 lets remote attackers pull other users' intermediate audio, video, and subtitle artifacts directly from the GET /api/tmp/:tmpFile and GET /api/music/:fileName endpoints, and delete any rendered video via the unauthenticated DELETE /api/short-video/:videoId endpoint. Reported by VulnCheck and rated CVSS 4.0 9.3, the flaw exposes both confidentiality and integrity of user job data with no login required. Publicly available exploit code exists, though there is no public exploit identified as being used in active attacks.

Technical ContextAI

OpenCode Studio is a self-hosted media/short-video generation application (Node/Express-style HTTP API) that stores per-job working files under a temp directory and a static/music directory. The vulnerability class is CWE-22 (Improper Limitation of a Pathname to a Restricted Directory / Path Traversal), compounded by missing authentication on API routes. The affected component is identified by CPE cpe:2.3:a:microck:opencode-studio and covers all versions prior to 2.4.4. The endpoints serve user-supplied path parameters (:tmpFile, :fileName, :videoId) straight into filesystem operations without an authentication gate and, per the vendor's own v2.4.4 notes, without validating that resolved names stay within their intended parent directory, allowing name-based traversal and cross-tenant access.

RemediationAI

Upgrade to OpenCode Studio v2.4.4 or later, which is the vendor-released patched version (fix commit 1f4d7a7f52beb43105d345b26fd0c0ffc2bf0004 and PR https://github.com/Microck/opencode-studio/pull/55); this release adds safeName validation rejecting path separators, traversal sequences, and absolute/empty names, and binds the server listener to 127.0.0.1 so unauthenticated endpoints are no longer network-reachable. If you cannot upgrade immediately, replicate the fix by binding the service to localhost (127.0.0.1) and placing it behind an authenticating reverse proxy, which removes remote reachability at the cost of breaking any legitimate LAN/remote access; additionally restrict or block external access to /api/tmp, /api/music, and /api/short-video at the proxy or firewall, accepting that this disables those API functions until patched. Consult the release notes and VulnCheck advisory (URLs above) before deploying, and note that localhost binding will break multi-host deployments that rely on network access to the API.