CVE-2026-130154 PUBLISHED

Zyrabit Platform: Path traversal in import_to_vault allows arbitrary file write and read via unvalidated destination_name/source_path

Assigner: GitHub_M
Reserved: 16.11.2026 Published: 18.11.2026 Updated: 19.11.2026

Zyrabit Platform provides sovereign AI infrastructure for enterprise retrieval-augmented generation. Prior to 2.4.4, import_to_vault(source_path, destination_name) accepts both caller-controlled paths, but the content-pattern guard does not confine destination_name. The vulnerable tool is implemented in zyrabit-slm/api-rag/app/domain/services/mcp_service.py, where Path(DOCS_DIR) / destination_name is passed to shutil.copy2, allowing traversal or an absolute destination to write outside the vault. An unrestricted source_path can be copied into the vault and retrieved through secure_query, disclosing files readable by the service; files that do not match the executable-pattern filter pass that filter. When ENABLE_LEGACY_EXTENSIONS=true, zyrabit-slm/api-rag/app/main.py registers POST /mcp/rpc without get_current_user, allowing unauthenticated network tool calls; this optional exposure is disabled by default and is not required for local invocation. If an attacker can stage chosen source content and write to an execution-triggered destination, the advisory describes conditional process execution. This issue is fixed in version 2.4.4.

Metrics

CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
CVSS Score: 9.1

Product Status

Vendor Zyrabit-tech
Product zyrabit-SLM
Versions
  • Version < 2.4.4 is affected

References

Problem Types

  • CWE-22: Improper Limitation of a Pathname to a Restricted Directory CWE
  • CWE-306: Missing Authentication for Critical Functionality CWE