CVE-2026-22253: Soft Serve is missing an authorization check in LFS lock deletion
LFS Lock Force-Delete Authorization Bypass Summary An authorization bypass in the LFS lock deletion endpoint allows any authenticated user with repository write access to delete locks owned by other users by setting the force flag. The vulnerable code path processes force deletions before retrieving user context, bypassing ownership validation entirely.
Published Jan 8, 2026
Affected packages
github.com/charmbracelet/soft-serve
- Ecosystem
- Go
- Affected
- < 0.11.2
- Fixed in
- 0.11.2
- Check
go list -m github.com/charmbracelet/soft-serve
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
LFS Lock Force-Delete Authorization Bypass
Summary
An authorization bypass in the LFS lock deletion endpoint allows any authenticated user with repository write access to delete locks owned by other users by setting the force flag. The vulnerable code path processes force deletions before retrieving user context, bypassing ownership validation entirely.
Severity
- CWE-863: Incorrect Authorization
- CVSS 3.1: 5.4 (Medium) —
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
Affected Code
File: pkg/web/git_lfs.go Function: serviceLfsLocksDelete (lines 831–945) Endpoint: POST /<repo>.git/info/lfs/locks/:lockID/unlock
The control flow processes req.Force at line 905 before retrieving user context at line 919:
// Line 905-916: Force delete executes immediately without authorization
if req.Force {
if err := datastore.DeleteLFSLock(ctx, dbx, repo.ID(), lockID); err != nil {
// ...
}
renderJSON(w, http.StatusOK, l)
return // Returns here, never reaching user validation
}
// Line 919: User context retrieved after force path has exited
user := proto.UserFromContext(ctx)Proof of Concept
Setup: Two users with write access to the same repository—User A (lock owner) and User B (attacker).
- User A creates a lock: ``
bash curl -X POST http://localhost:23232/repo.git/info/lfs/locks \ -H "Authorization: Basic <user_a_token>" \ -H "Content-Type: application/vnd.git-lfs+json" \ -d '{"path": "protected-file.bin"}'``
- User B deletes User A's lock using force flag: ``
bash curl -X POST http://localhost:23232/repo.git/info/lfs/locks/1/unlock \ -H "Authorization: Basic <user_b_token>" \ -H "Content-Type: application/vnd.git-lfs+json" \ -d '{"force": true}'``
- Result: Lock deleted successfully with
200 OK. Expected:403 Forbidden.
Suggested Fix
Retrieve user context and validate authorization before processing the force flag:
user := proto.UserFromContext(ctx)
if user == nil {
renderJSON(w, http.StatusUnauthorized, lfs.ErrorResponse{
Message: "unauthorized",
})
return
}
if req.Force {
if !user.IsAdmin() {
renderJSON(w, http.StatusForbidden, lfs.ErrorResponse{
Message: "admin access required for force delete",
})
return
}
if err := datastore.DeleteLFSLock(ctx, dbx, repo.ID(), lockID); err != nil {
// ...
}
renderJSON(w, http.StatusOK, l)
return
}Impact
Affected Deployments: Soft Serve instances with LFS enabled and repositories with multiple collaborators.
Exploitation Requirements:
- Authenticated session
- Write access to target repository
Consequences:
- Unauthorized deletion of other users' locks
- Bypass of LFS file coordination mechanisms
- Potential workflow disruption in collaborative environments
Limitations: Does not grant file access, escalate repository permissions, or affect repositories where the attacker lacks write access.
Credited to Tomer-PL.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesGHSA-f3fj-9625-rv3m
charmbracelet/soft-serve: Race in `SetPrivate` leaves a private repository readable by unauthenticated users
medium5.9Oct 30, 2026GHSA-fgxm-5hvv-x4vh
charmbracelet/soft-serve HTTP responses disclose the existence and names of private repositories
medium5.3Oct 30, 2026CVE-2026-33353
In Soft Serve, an authenticated repo import can clone server-local private repositories
high7.1Mar 19, 2026CVE-2026-30832
soft-serve vulnerable to SSRF via unvalidated LFS endpoint in repo import
critical9.1Mar 6, 2026CVE-2026-24058
Soft Serve Affected by an Authentication Bypass
high8.1Jan 21, 2026CVE-2025-64522
Soft Serve is vulnerable to SSRF through its Webhooks
critical9.1Nov 10, 2025
