CVE
zyrabit-SLM remote file read and write in import_to_vault
Affects zyrabit-SLM before 2.4.4. Unauthenticated network access requires the HTTP bridge enabled with ENABLE_LEGACY_EXTENSIONS=true. Fixed in 2.4.4.
- Exploited
- No known exploitation
- Fix
- Fixed in 2.4.4
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 2.4.4.
Summary
Zyrabit-tech's zyrabit-SLM, part of the Zyrabit Platform, has a path traversal flaw in its import_to_vault tool that lets an attacker remotely, without logging in, write files outside the document vault and read files the service can access. The flaw is fixed in later releases.
Original description
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.
Who should check
Teams running zyrabit-SLM (pip package zyrabit-slm) before 2.4.4, including any deployment using the import_to_vault agent tool or the MCP HTTP bridge.
“Path traversal in import_to_vault allows arbitrary file write and read via unvalidated destination_name/source_path (CWE-22)”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.1/10CVSS 9.1
- No patch0/5No signal
What would change the score
- Would score about 71 if added to CISA KEV
- Would score about 66 if CISA's SSVC rates exploitation active
- Would score about 31 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 2.4.4.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-130154 (Zyrabit Platform: Path traversal in import_to_vault allows arbitrary file write and read via unvalidated destination_name/source_path), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-130154 (entry last updated 2026-11-18):
Affected:
- Zyrabit-tech zyrabit-SLM: fixed in 2.4.4
Fixed versions: 2.4.4.
Conditions (all must be true for the bug to be hit):
- import_to_vault is a registered agent tool, so it can be reached through an agent. (source: https://github.com/Zyrabit-tech/zyrabit-SLM/security/advisories/GHSA-r4q8-hjfc-ggp2)
- Unauthenticated network access requires the HTTP bridge, enabled with ENABLE_LEGACY_EXTENSIONS=true. (source: https://github.com/Zyrabit-tech/zyrabit-SLM/security/advisories/GHSA-r4q8-hjfc-ggp2)
- The chained code-execution path needs attacker-staged content that does not trigger the executable-pattern filter. (source: https://github.com/Zyrabit-tech/zyrabit-SLM/security/advisories/GHSA-r4q8-hjfc-ggp2)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-130154 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130154 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/Zyrabit-tech/zyrabit-SLM/security/advisories/GHSA-r4q8-hjfc-ggp2
- https://github.com/Zyrabit-tech/zyrabit-SLM/pull/99
- https://github.com/Zyrabit-tech/zyrabit-SLM/commit/bb81be4d279a4680e26213c52041c003f9b78869
- https://github.com/Zyrabit-tech/zyrabit-SLM/releases/tag/v2.4.4
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-130154
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-130154"}.Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
Affected versions
- Zyrabit-tech zyrabit-SLM
fixed in 2.4.4
Evidence 6
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · Zyrabit-tech/zyrabit-SLM · Advisory GHSA-r4q8-hjfc-ggp2 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-130154 |
| Record | NVD · CVE-2026-130154 |
| Other links 3 | |
| Repository | GitHub · Zyrabit-tech/zyrabit-SLM · Pull request #99 |
| Repository | GitHub · Zyrabit-tech/zyrabit-SLM · Commit bb81be4d |
| Repository | GitHub · Zyrabit-tech/zyrabit-SLM · Release v2.4.4 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-130154
Is CVE-2026-130154 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The import_to_vault tool does not validate its destination_name and source_path inputs, so paths can point outside the intended vault. This allows reading arbitrary files the service can access, such as configuration, credentials and keys, and writing or overwriting files at arbitrary paths.Source: github.com
Which versions are affected by CVE-2026-130154?
zyrabit-SLM: before 2.4.4.Source: cve.now feed data
Am I affected, and how do I check?
Versions of zyrabit-SLM before 2.4.4 are affected. Unauthenticated network access needs the HTTP bridge, which is enabled only when ENABLE_LEGACY_EXTENSIONS=true, and import_to_vault is a registered agent tool that can be reached through an agent. To check a installation, look at the installed version and whether ENABLE_LEGACY_EXTENSIONS is set to true.Source: github.com
How do I fix CVE-2026-130154?
Upgrade zyrabit-SLM to 2.4.4 or later, which is the listed fixed version.Source: github.com