FlawAtlas
Search the atlas
CVE-2026-24058 High

Soft Serve Affected by an Authentication Bypass in github.com/charmbracelet/soft-serve

Soft Serve Affected by an Authentication Bypass in github.com/charmbracelet/soft-serve

Exploit probability 0.5%
Published February 2, 2026
Required by Not available
Last source change March 3, 2026

02 / AFFECTED SOFTWARE

Affected packages

Unknown Unknown

45 explicit affected versions

Go github.com/charmbracelet/soft-serve
Go github.com/charmbracelet/soft-serve

03 / CONNECTIONS

Connected vulnerabilities

related OPENSUSE-SU-2026:21483-1

04 / EVIDENCE

Source records

Open Source Vulnerabilities GO-2026-4353

Soft Serve Affected by an Authentication Bypass in github.com/charmbracelet/soft-serve

View original source
Open Source Vulnerabilities GHSA-pchf-49fh-w34r

### Impact _What kind of vulnerability is it? Who is impacted?_ This issue impacts every Soft Serve instance. A critical authentication bypass 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. ### Patches _Has the problem been patched? What versions should users upgrade to?_ Yes, please upgrade to version 0.11.3 as soon as possible. ### Workarounds _Is there a way for users to fix or remediate the vulnerability without upgrading?_ You need to upgrade

View original source
Open Source Vulnerabilities CVE-2026-24058

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.

View original source

05 / REFERENCES

Further evidence