CVE-2026-130154
Zyrabit vault imports could read or overwrite files outside the vault
Zyrabit-tech · zyrabit-SLM
First documented disclosure · Review checkpoint
Summary
A caller-controlled import could copy readable files into the vault or write beyond its directory.
Severity and exploitation evidence
Critical · 9.1/10 · CVSS 3.1. Severity source.
Exploitation not established: Malicious exploitation remains unverified in the reviewed originals. A demonstration or absence from KEV does not establish exploitation status.
Technical severity is not a measure of observed attacks or of risk to your deployment. Attempts, demonstrations, and successful compromise retain the qualifications in the source.
How the weakness works
The content-pattern filter did not constrain either filesystem path.
Conditions required
Ability to invoke import_to_vault; unauthenticated HTTP invocation additionally requires ENABLE_LEGACY_EXTENSIONS=true, disabled by default.
Potential impact
Readable service files can be disclosed through vault queries. Writable destinations can be overwritten; code execution additionally requires attacker-staged content and an execution trigger.
Affected versions and configurations
zyrabit-SLM: < 2.4.4.
Fix and mitigation status
2.4.4.
Practical next steps
Apply the issue-specific correction: 2.4.4. Restrict the affected tool or endpoint until the correction is deployed.
Operating lesson
Constrain both source and destination paths and authenticate optional tool transports.
Evidence and limits
Earliest reviewed public evidence 2026-09-13; CVE publication 2026-11-18. CVSS 3.1 9.1 is attributed to GitHub_M in the CNA record.
Sources
- GitHub_M CVE authority record
Primary source ·
- Maintainer security advisory
Primary source ·
- Original correction or vendor bulletin
Primary source ·
- Original correction or vendor bulletin
Primary source ·