dbcve.org
Path TraversalWeakness · CWE-22

CVE-2025-58355

HIGH · 7.7 CVSS v3.1 Published 2025-09-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
83/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Soft Serve is a self-hostable Git server for the command line. In versions 0.9.1 and below, attackers can create or override arbitrary files with uncontrolled data through its SSH API. This issue is fixed in version 0.10.0.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Soft Serve Git server versions 0.9.1 and below contain a file write vulnerability in its SSH API that allows authenticated or unauthenticated attackers (depending on configuration) to create or overwrite arbitrary files on the host system with uncontrolled data.

MitigationUpgrade to Soft Serve version 0.10.0 or later. Until patched, restrict SSH access to trusted users only and monitor for unauthorized file creation activity.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Soft Serve installation
    Check for running Soft Serve processes (ps aux | grep soft-serve) or listening services on common SSH ports (22, 2222). If running as a systemd service, check with: systemctl list-units --type=service | grep -i serve
    Affected if Soft Serve process or service is found running on the system
  2. Determine installed Soft Serve version
    Run 'soft-serve version' if the binary is in PATH, or check the version from the binary/package that was installed (e.g., dpkg -l, rpm -qi, or docker images ls)
    Affected if Version is 0.9.1 or below, or version cannot be determined and the binary is likely older than 0.10.0
  3. Verify SSH API accessibility
    Review Soft Serve configuration file (default location ~/.config/softserve/softserve.yaml or /etc/softserve/softserve.yaml) for ssh.listen_addr and public_key_auth settings. Check if SSH port is exposed to network interfaces other than localhost
    Affected if SSH API is bound to a reachable network address and accepts connections from untrusted networks
  4. Confirm authentication settings
    Inspect the configuration for 'anonymous' or 'public_key_auth' settings. Determine if unauthenticated access is permitted or if only authenticated users can access the SSH API
    Affected if Unauthenticated access is enabled OR SSH access is granted to untrusted/non-admin users
  5. Audit for unauthorized file creation
    Review system logs (journalctl -u soft-serve, /var/log/auth.log, or SSH daemon logs) for unusual file write operations or git-receive-pack/git-upload-pack activity that may indicate exploitation attempts
    Affected if Logs show file creation or modification events originating from Soft Serve that were not initiated by legitimate administrators

A system is affected if it runs Soft Serve version 0.9.1 or below with SSH API access enabled to untrusted users, either authenticated or unauthenticated.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Soft Serve version 0.10.0 or later. Until patched, restrict SSH access to trusted users only and monitor for unauthorized file creation activity.

Recommended fix Moderate confidence

0.10.0

  1. Check current installed version of Soft Serve
  2. Backup all configuration files, repositories, and data
  3. Obtain Soft Serve version 0.10.0 from the official GitHub repository (github.com/charmbracelet/soft-serve)
  4. Follow the installation/upgrade instructions for your deployment method (binary, Docker, source, etc.)
  5. Restart the Soft Serve service
  6. Verify the new version is 0.10.0
  7. Test that SSH access works correctly and that the path traversal vulnerability is no longer present

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-58355 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-58355 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data