External risk intelligence

OpenCode Studio Unauthenticated File Read and Delete Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.3)

CVE-2026-69110

The vulnerability resides in API endpoints designed for file and media operations. As an application that processes jobs and media, these API endpoints are commonly exposed to the internet to facilitate remote client interactions and web-based functionality, making them a likely target for external access in standard deployments.

Path Traversal

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A vulnerability in OpenCode Studio allows unauthenticated remote attackers to access sensitive files and delete user data. This issue arises from missing authentication on specific API endpoints, enabling unauthorized users to retrieve intermediate job artifacts and manipulate video content.

Unauthorized access to user files and data.
Critical system exposure without any credentials.
Confirm relevance and potential exposure.

Attack Path

How an attacker could exploit the issue

An attacker can exploit this vulnerability by directly accessing specific API endpoints over the network without needing any credentials. This exposure allows them to read sensitive temporary files or media artifacts created by other users, and potentially delete video content.

No authentication required.
Direct access to API endpoints.
Sensitive file and video data exposed.

Live Threat

Current exploitation, exposure, and threat context

Unauthenticated attackers could access and delete arbitrary files within the temp and static/music directories. This could occur when specific API endpoints are directly accessed, potentially exposing intermediate audio, video artifacts, and subtitles belonging to other users' jobs.

Intermediate job artifacts at risk.
Direct API access could expose files.
Unauthorized data retrieval and deletion.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability in OpenCode Studio likely falls under the responsibility of application owners and platform teams, as it affects core API functionalities for file and media processing. The immediate first step is to inventory all instances of OpenCode Studio, confirm their accessibility and business criticality, and identify the specific application or service owners. Once identified, a risk-based remediation plan should be developed, prioritizing critical and exposed systems.

Identify accountable application owners.
Verify external accessibility and impact.
Plan remediation based on risk.

Supplementary metadata

CVSS vector

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Free EASM Trial See How Signal Works

Frequently asked questions

What is OpenCode Studio used for?

OpenCode Studio is a software platform designed for media processing and job management. It enables users to create, manipulate, and store various audio and video assets. Because it handles intermediate work artifacts like subtitles and media files, it serves as a collaborative environment where multiple users or automated services might process content simultaneously.

What does CWE-22 mean for CVE-2026-69110?

CVE-2026-69110 is classified as CWE-22, commonly known as Improper Limitation of a Pathname to a Restricted Directory. In plain terms, this means the software fails to properly check if a file request is authorized. Because of this weakness, the application allows users to request files from directories they should not be able to access, effectively bypassing intended security boundaries to read or delete sensitive data.

How do attackers trigger this vulnerability?

An attacker triggers this flaw by sending direct requests to specific API endpoints without providing any authentication credentials. The vulnerability is triggered solely by accessing the GET endpoints for temporary files or music, and the DELETE endpoint for videos. Simply browsing the main application interface or authenticating normally does not trigger the bug; it requires targeted interaction with these specific, unprotected API paths.

Do I need to worry if my OpenCode Studio is internal?

Halo Surface Signal indicates that this vulnerability is highly relevant if your deployment is internet-facing, as these API endpoints are often exposed to support remote functionality. Even if your instance is internal, the risk remains if the API is reachable by other users or services within your network. You should prioritize assessing whether your configuration allows these sensitive endpoints to be reached by untrusted traffic.

Why should I update my OpenCode Studio?

Updating is necessary because the current version lacks the required security checks to prevent unauthorized data access and deletion. Your first step should be to inventory all instances of the software and confirm if they are running a version earlier than 2.4.4. Once identified, work with your platform team to apply the patch, which restores mandatory authentication and protects your users' media and job artifacts from unauthorized manipulation.

References

Written by Nicholas Merritt

Nicholas Merritt is VP of Security Solutions at Halo Security. With more than 25 years across application security, vulnerability prioritization, and offensive security, he helps teams translate threat data into practical exposure validation and remediation focus. He authors Halo Threat Intelligence CVE advisories using Halo Surface Signal and H/A/L/O context to prioritize internet-facing risk.