dbcve.org
Soft ServeApplication · Charm

CVE-2026-24058

CRITICAL · 9.8 CVSS v3.1 Published 2026-01-22
Fix available
A fix is available. Upgrade to 0.11.3 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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. Versions 0.11.2 and below have a critical authentication bypass vulnerability that allows an attacker to impersonate any user (including admin) by "offering" the victim's public key during the SSH handshake before authenticating with their own valid key. This occurs because the user identity is stored in the session context during the "offer" phase and is not cleared if that specific authentication attempt fails. This issue has been fixed in version 0.11.3.

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.11.2 and below contain an authentication bypass where an attacker can offer a victim's public key during the SSH handshake before authenticating with their own valid key. The user identity is stored in the session context during the 'offer' phase and is not cleared if that authentication attempt fails, allowing impersonation of any user including admin.

MitigationUpgrade to version 0.11.3 or later. If immediate upgrade is not possible, restrict SSH access to trusted networks and monitor for suspicious authentication patterns.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Soft ServeApplication
Affected:< 0.11.3

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Check installed Soft Serve version
    Run 'soft-serve --version' or check the binary version with 'soft-serve -v' or inspect the installed package via your package manager (e.g., 'apt list --installed | grep soft-serve' or 'brew list soft-serve')
    Affected if The installed version is 0.11.2 or below, or the version cannot be determined (unknown) and you are using SSH authentication
  2. Confirm SSH access is enabled
    Check the Soft Serve configuration file (default: ~/.softserve/config.yaml or /etc/softserve/config.yaml) for SSH server settings, or verify the SSH daemon is running with 'ps aux | grep soft-serve' or 'systemctl status soft-serve'
    Affected if SSH access is enabled and the version is vulnerable as above
  3. Review authentication logs for anomalies
    Examine Soft Serve logs (typically in ~/.softserve/logs/ or via journalctl for systemd) for failed authentication attempts that succeeded after offering a different user's public key, or check SSH auth logs for out-of-order key offerings
    Affected if Logs show authentication failures followed by successful sessions with different key identities, or unexpected user identity changes during SSH handshake

You are affected if Soft Serve version is 0.11.2 or below and SSH authentication is enabled, allowing an attacker to impersonate users via the public key offer race condition.

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
Upgrade available Upgrade to 0.11.3 or later
Fixed in 0.11.3
Vendor patch github.com →
Interim mitigation

Upgrade to version 0.11.3 or later. If immediate upgrade is not possible, restrict SSH access to trusted networks and monitor for suspicious authentication patterns.

Recommended fix High confidence

0.11.3

  1. 1. Stop the Soft Serve service if it is currently running
  2. 2. Upgrade Soft Serve to version 0.11.3 or later
  3. 3. Verify the installed version matches or exceeds 0.11.3
  4. 4. Restart the Soft Serve service

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

Fix this in Soft Serve Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-24058 — 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-2026-24058 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