External risk intelligence

Knowns Directory Traversal Via X-Opencode-Directory Header

CVE advisorySeverity: CRITICAL (CVSS 9.3)

CVE-2026-88899

The vulnerability exists in an API endpoint (/api/opencode) acting as a proxy. API endpoints are commonly exposed as internet-facing services or gateways in modern application deployments to facilitate external communication and functionality.

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 critical vulnerability has been identified in the /api/opencode proxy endpoint, which could allow remote attackers to execute file operations outside the intended project directory on the host system. This issue stems from improper validation of a specific request header.

  • Directory control issue in an API proxy.
  • Matters if external systems interact with this API.
  • Confirm relevance and exposure of this proxy endpoint.

Attack Path

How an attacker could exploit the issue

An attacker could exploit this vulnerability by sending a specially crafted request to the `/api/opencode` endpoint. This request would target the `x-opencode-directory` header, which is not properly validated. If successful, an attacker could manipulate file operations on the host system, potentially leading to unauthorized execution of code or access to sensitive data.

  • Network access to the API endpoint is required.
  • A crafted request to the `/api/opencode` endpoint triggers the vulnerability.
  • Enables arbitrary file operations outside the project.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could allow an unauthenticated attacker to execute arbitrary file operations outside of a project's root directory on the host system. This is possible when the affected system processes requests to the `/api/opencode` proxy endpoint without properly validating the `x-opencode-directory` header.

  • Host file system access.
  • Via manipulated request headers.
  • Unauthorized file operations on host.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability resides in an API endpoint commonly exposed externally. Application owners or platform teams are likely responsible for managing this technology. The first step is to inventory all instances of the affected technology, assess their exposure, and identify the business-critical systems to prioritize remediation efforts.

  • Application and platform teams own the issue.
  • Verify external exposure and critical systems first.
  • Plan remediation based on identified risk.

Supplementary metadata

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.

Frequently asked questions

What is the Knowns software?

Knowns is an application framework often used to manage project-based environments and developer workflows. It includes proxy components like the /api/opencode endpoint, which helps bridge communication between external requests and internal file systems. This software is typically deployed in infrastructure where automated code handling and project management are required.

What does CVE-2026-88899 mean for file security?

This vulnerability is classified as CWE-73: External Control of File Name or Path. Essentially, the software fails to sanitize user-supplied input in a specific HTTP header. This allows an attacker to break out of the intended project directory and interact with other files or directories on the underlying host system that the application process has permission to access.

How is this vulnerability triggered?

An attacker triggers this flaw by sending a network request to the /api/opencode endpoint with a maliciously crafted x-opencode-directory header. If the system does not properly validate this header, it will follow the path provided by the attacker instead of staying within the project root. Requests that do not reach this specific proxy endpoint or that use standard, valid header values do not trigger this file system manipulation.

Is my system at risk?

You should consider the risk if your instances are accessible over the network. According to Halo Surface Signal, the /api/opencode endpoint acts as a proxy, and such API gateways are frequently configured as internet-facing services to enable external connectivity. If your deployment exposes this endpoint to unauthorized networks, it is a primary target for exploitation.

How do I respond to this vulnerability?

Begin by identifying all running instances of Knowns within your environment and mapping which ones are reachable from external networks. Focus your immediate efforts on securing or restricting access to the /api/opencode endpoint on these systems. Once the footprint is understood, prioritize updating to version 0.31.0 or later, which contains the necessary validation logic to prevent unauthorized file path traversal.

References