CVE-2026-52799
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedGogs is an open source self-hosted Git service. Prior to 0.14.3, GET /attachments/:uuid returns the raw attachment file without verifying whether the requester has view permission for the associated Issue/Comment/Release or the repository. In a test environment with REQUIRE_SIGNIN_VIEW = false, we confirmed that an unauthenticated user can download attachments belonging to a private repository. This vulnerability is fixed in 0.14.3.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Gogs attachment download endpoint (/attachments/:uuid) prior to version 0.14.3 does not verify whether the requester has view permission for the associated Issue, Comment, Release, or the repository itself. This allows unauthenticated users (or authenticated users without proper permissions) to download attachments from private repositories by knowing or guessing the attachment UUID.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Gogs installation and versionCheck the Gogs version by accessing the /api/v1/version endpoint, viewing the admin dashboard 'About' page, or running 'gogs --version' if you have CLI access. Also check the gogs.ini configuration file for version metadata.Affected if The installed version is prior to 0.14.3 (e.g., 0.14.2, 0.14.1, 0.13.x, etc.)
-
Confirm attachment storage is configuredInspect the Gogs configuration file (custom/conf/gogs.ini or /etc/gogs/gogs.ini) for the [attachment] section. Verify that 'storage' is not set to 'disable' and that a valid path is configured under 'path' or 'minio' settings.Affected if Attachments are enabled in the configuration (the vulnerability only applies when attachments are allowed)
-
Check for private repositories with attachmentsReview the Gogs database or file system. Examine the /attachments directory (default: ~gogs/gogs/data/attachments) for uploaded files. Use the Gogs admin panel or database query to list private repositories that have issues, comments, or releases containing attachments.Affected if Private repositories exist with associated attachments; the flaw allows unauthorized access to these files
You are affected if Gogs version is below 0.14.3 AND attachment storage is enabled AND your Gogs instance hosts private repositories with uploaded attachments.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade Gogs to version 0.14.3 or later to obtain the fix that adds proper permission verification before serving attachment files.
0.14.3
- Upgrade Gogs to version 0.14.3 or later to address the IDOR vulnerability in the /attachments/:uuid endpoint
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-52799 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-52799 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data