LiveActive security incident?Get immediate response
CVE Record

CVE-2026-22253: Soft Serve is missing an authorization check in LFS lock deletion

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.

MediumCVSS 5.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Soft Serve versions before 0.11.2 let an authenticated user with repository write access delete Git LFS locks owned by other users. This can disrupt collaboration or override lock-based workflow controls, but it does not expose data directly. The vendor states the issue is patched in 0.11.2.

Executive priority

Treat as a routine but timely update for teams relying on Soft Serve and Git LFS locking. Business risk is collaboration disruption and unauthorized removal of workflow protections, not broad system compromise based on current sources.

Technical view

CVE-2026-22253 is a CWE-863 missing authorization check in Charmbracelet Soft Serve. The LFS lock deletion path handles forced deletions before loading user context, bypassing ownership validation. Scope is network-accessible, low-complexity, authenticated access with repository write privileges. CVSS 3.1 score is 5.4.

Likely exposure

Organizations running self-hosted Charmbracelet Soft Serve before 0.11.2 are potentially exposed, especially where multiple users have write access to repositories using Git LFS locks.

Exploitation context

The source bundle does not show public exploitation or CISA KEV listing. Exploitation requires a valid authenticated account with repository write access. Impact is limited to integrity and availability of LFS lock workflows.

Researcher notes

The advisory and commit indicate the flaw is authorization bypass in forced LFS lock deletion ordering. Validate only against owned test instances. Evidence currently supports affected versions before 0.11.2 and a vendor patch in 0.11.2; no active exploitation source is provided.

Mitigation direction

  • Upgrade Charmbracelet Soft Serve to version 0.11.2 or later.
  • Review the GitHub security advisory for vendor-specific guidance.
  • Reduce unnecessary repository write access until affected instances are upgraded.

Validation and detection

  • Inventory all Soft Serve instances and record their versions.
  • Flag any instance running Soft Serve earlier than 0.11.2.
  • Identify repositories using Git LFS locks and users with write access.
  • Review available audit logs for unusual LFS lock deletion activity.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-863: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Privilege behavior lookup

The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-22253 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.4 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L2.82.5Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.4Medium
CVSS 3.1 vector shape for CVE-2026-22253Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
charmbraceletsoft-serve< 0.11.2Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-863 · source CWE mapping

Incorrect Authorization

Incorrect Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.