Skip to main content
VulnerabilityPublished

CVE-2026-130154: zyrabit-SLM · Path Traversal

Affects zyrabit-SLMSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.1 Critical : upgrade to 2.4.4 as a priority.

Data as of 18 Nov 2026, 17:05 UTC

CVSS 3.1 base score
9.1Critical
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.19.1
Patch
Available – fixed in 2.4.4
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.

What to do

Upgrade zyrabit-SLM to 2.4.4.

Affected software

ProductAffectedFixed in
Zyrabit-techzyrabit-SLMAffected
  • <2.4.4
Fixed in
  • 2.4.4

AI-suggested

Upgrade to zyrabit-SLM version 2.4.4 or later, where this vulnerability is fixed. If using ENABLE_LEGACY_EXTENSIONS, ensure it remains disabled unless absolutely necessary, as it exposes an unauthenticated network interface. No other mitigations are specified or required once patched.

Description

Zyrabit-tech zyrabit-SLM versions prior to 2.4.4 contain a critical path traversal vulnerability in the import_to_vault function. This flaw allows an attacker to write files outside the intended vault directory by manipulating the destination path, potentially leading to unauthorized file disclosure and execution. An optional unauthenticated network interface increases exposure when enabled but is disabled by default. The issue is fixed in version 2.4.4.

References

Community reviews

Loading reviews…