The vulnerability CVE-2026-30832 in charmbracelet's soft-serve Git server arises from insufficient validation of user-controlled URLs in the Large File Storage (LFS) import functionality. Specifically, authenticated SSH users can supply a crafted --lfs-endpoint URL during the 'repo import' command that causes the server to perform HTTP requests to arbitrary internal or private IP addresses. This SSRF vulnerability (CWE-918) allows attackers to bypass network segmentation and access internal services that are otherwise inaccessible externally. The initial HTTP request made by the server is blind, as the response from the metadata endpoint does not parse as valid LFS JSON, limiting immediate data leakage. However, attackers can host a fake LFS server that returns download URLs pointing to internal resources, enabling chained requests that provide full read access to internal services. This can lead to unauthorized data disclosure and potential further exploitation within the internal network. The vulnerability affects all soft-serve versions from 0.6.0 up to 0.11.4 and requires authenticated SSH access, which limits the attack surface but still poses a significant risk in environments where user credentials are compromised or users are malicious insiders. The issue has been addressed in version 0.11.4 by implementing proper validation and restrictions on the URLs used in the LFS import process. The CVSS v3.1 score of 9.1 reflects the critical nature of this vulnerability, considering its network attack vector, low complexity, required privileges, no user interaction, and the potential for high confidentiality impact with partial integrity and availability impact. No public exploits have been reported yet, but the vulnerability's characteristics make it a high priority for patching.

This SSRF vulnerability can have severe consequences for organizations using soft-serve as their self-hosted Git server. Attackers with authenticated SSH access can exploit this flaw to access internal services that are typically protected by network segmentation or firewalls, potentially exposing sensitive internal data, configuration files, or credentials. This can lead to lateral movement within the network, further compromise of internal systems, and data breaches. The ability to read internal services undermines confidentiality and can also affect integrity if attackers leverage the access to manipulate internal resources indirectly. Availability may be impacted if internal services are overwhelmed or manipulated through crafted requests. Organizations relying on soft-serve for source code management and internal DevOps workflows face risks of intellectual property theft, disruption of development processes, and exposure of internal infrastructure details. Since the vulnerability requires authenticated SSH access, the risk is heightened in environments with weak access controls, compromised user credentials, or insider threats. The lack of known exploits in the wild currently reduces immediate risk but does not diminish the urgency of remediation given the critical CVSS rating and potential impact.

Organizations should immediately upgrade all affected soft-serve instances to version 0.11.4 or later, where the vulnerability has been patched. In addition to patching, organizations should enforce strict SSH access controls, including multi-factor authentication and monitoring of SSH sessions to detect suspicious activities. Network segmentation should be reviewed to limit the ability of internal services to be accessed via the Git server, and outbound HTTP requests from the soft-serve server should be restricted or monitored to detect anomalous behavior. Implementing web application firewalls (WAFs) or intrusion detection systems (IDS) that can identify SSRF patterns may provide additional defense layers. Regular audits of user privileges and repository import operations can help detect misuse. If upgrading immediately is not feasible, consider disabling the LFS import functionality or restricting its use to trusted users only. Logging and alerting on unusual LFS endpoint URLs or unexpected HTTP requests originating from the soft-serve server can aid in early detection of exploitation attempts. Finally, organizations should educate developers and administrators about the risks of SSRF and the importance of applying security updates promptly.