Vulnerability · Published Jun 24, 2026 · Assigned by GitHub_M

CVE-2026-52812Gogs: LFS dedupe path leaks private repo content across tenants

High 7.1

In plain English

A high-severity insufficient verification of data authenticity in gogs from gogs. Proof-of-concept exploit code is public. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 15% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS 4.0)7.1High
Exploit odds (30 days)0.2%top 85.3% of all CVEs
Exploited in the wildNo reportsCISA SSVC: poc
Attack toolingNoneno public tooling known

Official description

Gogs is an open source self-hosted Git service. Prior to 0.14.3, Git LFS storage is content-addressed by OID alone (<LFS-root>/<oid[0]>/<oid[1]>/<oid>) but per-repo authorization lives in the lfs_object table keyed (repo_id, oid). serveUpload skips re-uploading when the OID file already exists on disk and inserts a new (repo_id, oid) row pointing at it without verifying the request body hashes to the OID being claimed. Any user with write access to one repo can bind their repo to an OID owned by a private repo and download the original bytes via their own download endpoint. This vulnerability is fixed in 0.14.3.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Gogogs.io/gogs0.14.3GHSA-6p9m-q3jp-47h4
Gogogs.io/gogsno fix listedGO-2026-5184

Affected products (as reported)

VendorProductVersions
gogs gogs < 0.14.3

Weakness: CWE-345, CWE-639, CWE-862 · Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:L/SI:N/SA:N

References