Cross-repository metadata disclosure via global lock IDs
Published Sep 15, 2026 · Updated Sep 15, 2026
Authorization bypass in Charmbracelet Soft Serve 0.7.1 through 0.11.6 allows remote authenticated users to read private lock metadata. The HTTP Git LFS list and unlock handlers pass an attacker-controlled global lock ID to a store query that omits the repository ID. Write access to any repository is sufficient to expose locked paths, usernames, timestamps, and lock existence from inaccessible repositories; file contents remain protected and no data is changed.
Summary
What happened
Authorization bypass in Charmbracelet Soft Serve 0.7.1 through 0.11.6 allows remote authenticated users to read private lock metadata. The HTTP Git LFS list and unlock handlers pass an attacker-controlled global lock ID to a store query that omits the repository ID. Write access to any repository is sufficient to expose locked paths, usernames, timestamps, and lock existence from inaccessible repositories; file contents remain protected and no data is changed.
The record
- CVE
- CVE-2026-91773
- Published
- Sep 15, 2026
- Updated
- Sep 15, 2026
- Vendor
- Charmbracelet
- Product
- Soft Serve
- Classifications
- CWE-639, T1213.003
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 15, 2026CVE publishedPublication date reported by the CVE source.
- Sep 15, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0.7.1 <0.12.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Global Git LFS lock ID enumeration requestproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo