External risk intelligence

Zyrabit Platform Path Traversal and Unauthenticated API Access Vulnerability.

CVE advisorySeverity: CRITICAL (CVSS 9.1)

CVE-2026-130154

The vulnerability exists in an API service for an enterprise AI infrastructure platform. While the component typically handles internal retrieval-augmented generation tasks, it includes an optional, disabled-by-default configuration that exposes an unauthenticated POST endpoint. Because public exposure is not the default or intended state for this specific function, it is categorized as possible rather than likely.

Path Traversal

Halo Surface Signal: 3 out of 5 — possibly public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This CVE affects the Zyrabit Platform, which provides AI infrastructure for enterprises. A vulnerability in a file import function could allow unauthorized access to sensitive files or potentially enable the execution of code if a specific, optional setting is enabled. The main concern is to confirm if this specific platform is in use and if the optional setting is activated.

  • Sensitive files may be exposed or accessed.
  • Confirm if Zyrabit AI platform is deployed.
  • Assess platform usage and optional settings.

Attack Path

How an attacker could exploit the issue

An attacker could exploit this vulnerability by directing the platform to import arbitrary files into its secure vault, and then potentially retrieving them for disclosure. If a legacy extension feature is enabled, an attacker could also trigger process execution by staging specific content and writing it to a designated location.

  • Unauthenticated network access or local access required.
  • Importing arbitrary files via `import_to_vault`.
  • Confidentiality, integrity, and conditional execution risks.

Live Threat

Current exploitation, exposure, and threat context

When the optional legacy extension is enabled, unauthenticated network requests could lead to unauthorized file disclosures and potentially condition process execution. This could affect system files readable by the service and files that bypass content filters.

  • System files readable by service.
  • Unrestricted source path allows writing.
  • Conditional process execution is possible.

Operational Fix

Recommended remediation, mitigation, and detection steps

The Zyrabit Platform's AI infrastructure, specifically the `import_to_vault` function, is vulnerable to path traversal and potential unauthorized file disclosure or execution. This could impact application owners and platform teams responsible for the AI infrastructure. The immediate first step is to identify all Zyrabit Platform deployments, confirm their reachability and criticality, and then assign ownership for remediation planning.

  • Application and platform teams own the issue.
  • Verify Zyrabit Platform deployment reachability and criticality.
  • Plan remediation based on identified risk and ownership.

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 Zyrabit Platform?

The Zyrabit Platform is an enterprise-grade AI infrastructure designed to support retrieval-augmented generation. It allows organizations to manage, store, and process documents within a secure vault, enabling AI models to retrieve relevant data for generating responses based on an organization's internal knowledge base.

How does CVE-2026-130154 create a security weakness?

This vulnerability involves Path Traversal (CWE-22) and Missing Authentication for Critical Function (CWE-306). The system fails to properly validate destination paths when importing files, which allows attackers to write files outside of the intended secure directory. Additionally, when legacy features are active, the platform allows sensitive operations to proceed without verifying the user's identity.

Does my system trigger this vulnerability by default?

Not necessarily. The file-handling flaw requires an attacker to successfully manipulate file paths during the import process. Furthermore, the most dangerous scenario—unauthenticated network access—only occurs if you have manually enabled the legacy extension feature. If this optional setting remains disabled, the platform does not expose the vulnerable API endpoint to the network.

Is my deployment at risk according to Halo Surface Signal?

Halo Surface Signal labels the risk as Possible. Because the vulnerability exists within an API service designed primarily for internal retrieval tasks, it is not intended to be internet-facing. Your risk level depends on whether you have enabled the optional, disabled-by-default legacy configuration that would expose these internal functions to the broader network.

What is the first step to remediate this issue?

The essential first step is to upgrade your Zyrabit Platform instance to version 2.4.4 or later. In parallel, audit your environment to determine if the legacy extension settings are enabled. If you cannot update immediately, ensure that any services utilizing the affected API are strictly firewalled and isolated from untrusted network segments.

References