Repository takeover via relative-path sanitization failure
Published Jan 8, 2025 · Updated Jan 8, 2025
Path traversal in Charmbracelet Soft Serve before 0.8.2 allows remote authenticated users to take over other users' repositories. SanitizeRepo cleaned an untrusted relative repository name without first anchoring it to an absolute path, preserving leading traversal segments for repository-management paths. Only multi-user deployments that let users create repositories are exposed; an existing non-admin user can modify or delete another user's repository.
Summary
What happened
Path traversal in Charmbracelet Soft Serve before 0.8.2 allows remote authenticated users to take over other users' repositories. SanitizeRepo cleaned an untrusted relative repository name without first anchoring it to an absolute path, preserving leading traversal segments for repository-management paths. Only multi-user deployments that let users create repositories are exposed; an existing non-admin user can modify or delete another user's repository.
The record
- CVE
- CVE-2025-22130
- Published
- Jan 8, 2025
- Updated
- Jan 8, 2025
- Vendor
- Charmbracelet
- Product
- Soft Serve
- Classifications
- CWE-22, T1485, T1565.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 8, 2025CVE publishedPublication date reported by the CVE source.
- Jan 8, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 0.8.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo