CVE-2026-22253
published 2026-01-08CVE-2026-22253: Soft Serve is a self-hostable Git server for the command line. Prior to version 0.11.2, an authorization bypass in the LFS lock deletion endpoint allows any…
PriorityP432medium5.4CVSS 3.1
AVNACLPRLUINSUCNILAL
EPSS
0.27%
19.0th percentile
Soft Serve is a self-hostable Git server for the command line. Prior to version 0.11.2, 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. This issue has been patched in version 0.11.2.
Affected
3 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| charm | soft_serve | < 0.11.2 | 0.11.2 |
| charmbracelet | soft-serve | < 0.11.2 | 0.11.2 |
| github.com | charmbracelet_soft-serve | >= 0 < 0.11.2 | 0.11.2 |
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
OSV
Soft Serve is missing an authorization check in LFS lock deletion in github.com/charmbracelet/soft-serve
osv·2026-01-12
CVE-2026-22253 Soft Serve is missing an authorization check in LFS lock deletion in github.com/charmbracelet/soft-serve
Soft Serve is missing an authorization check in LFS lock deletion in github.com/charmbracelet/soft-serve
Soft Serve is missing an authorization check in LFS lock deletion in github.com/charmbracelet/soft-serve
OSV
Soft Serve is missing an authorization check in LFS lock deletion
osv·2026-01-08
CVE-2026-22253 [MEDIUM] Soft Serve is missing an authorization check in LFS lock deletion
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.
### 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 /.git/info/lfs/locks/:lockID/unlock`
The control flow processes `req.Force` at line 905 before retrieving us
GHSA
Soft Serve is missing an authorization check in LFS lock deletion
ghsa·2026-01-08
CVE-2026-22253 [MEDIUM] CWE-863 Soft Serve is missing an authorization check in LFS lock deletion
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.
### 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 /.git/info/lfs/locks/:lockID/unlock`
The control flow processes `req.Force` at line 905 before retrieving us
No detection rules found.
No public exploits indexed.
2026-01-08
Published