CVE-2026-52799

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 66% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Gogs 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.

CVSS v3
7.5
EG Score
7.5(medium)
EPSS
34.0%
KEV
Not listed

Published

June 22, 2026

Last Modified

June 25, 2026

Advisory Details (2)

Auto-updated Jun 24, 2026
Patch available. Sources: github_release, github.
github Patch Available

Missing Authorization in Attachment Download · Advisory · gogs/gogs · GitHub

https://github.com/gogs/gogs/security/advisories/GHSA-p9f5-h3rx-j5qw
github_release Patch Available

0.14.3

Patch available: gogs/gogs v0.14.3

https://github.com/gogs/gogs/releases/tag/v0.14.3

Vendor Advisories for CVE-2026-52799(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
gogs.io/gogs—0.14.3—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 21× in last 7d / 43× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-07 06:57 UTCEG score recompute
  2. 2026-07-06 18:45 UTCEG score recompute
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 05:44 UTCEG score recompute
  6. 2026-07-06 02:23 UTCEPSS rescore
  7. 2026-07-05 17:29 UTCEG score recompute
  8. 2026-07-05 05:18 UTCEG score recompute
  9. 2026-07-05 02:30 UTCEPSS rescore
  10. 2026-07-04 17:02 UTCEG score recompute
  11. 2026-07-04 06:31 UTCEPSS rescore
  12. 2026-07-04 04:49 UTCEG score recompute
  13. 2026-07-03 16:35 UTCEG score recompute
  14. 2026-07-03 04:24 UTCEG score recompute
  15. 2026-07-02 16:12 UTCEG score recompute
  16. 2026-07-02 04:01 UTCEG score recompute
  17. 2026-07-01 15:48 UTCEG score recompute
  18. 2026-07-01 15:07 UTCEPSS rescore
  19. 2026-07-01 03:37 UTCEG score recompute
  20. 2026-06-30 23:22 UTCEPSS rescore
  21. 2026-06-30 15:25 UTCEG score recompute
  22. 2026-06-30 03:14 UTCEG score recompute
  23. 2026-06-29 15:03 UTCEG score recompute
  24. 2026-06-29 14:06 UTCEPSS rescore
  25. 2026-06-29 14:06 UTCEPSS rescore
Show 18 more
  1. 2026-06-29 02:52 UTCEG score recompute
  2. 2026-06-28 14:41 UTCEG score recompute
  3. 2026-06-28 14:07 UTCEPSS rescore
  4. 2026-06-28 04:56 UTCEPSS rescore
  5. 2026-06-28 04:56 UTCEPSS rescore
  6. 2026-06-28 02:30 UTCEG score recompute
  7. 2026-06-27 14:19 UTCEG score recompute
  8. 2026-06-27 03:08 UTCEPSS rescore
  9. 2026-06-27 02:08 UTCEG score recompute
  10. 2026-06-26 13:56 UTCEG score recompute
  11. 2026-06-26 01:42 UTCEG score recompute
  12. 2026-06-25 13:49 UTCEPSS rescore
  13. 2026-06-25 13:31 UTCEG score recompute
  14. 2026-06-25 01:19 UTCEG score recompute
  15. 2026-06-24 13:08 UTCEG score recompute
  16. 2026-06-24 00:56 UTCEG score recompute
  17. 2026-06-23 12:44 UTCEG score recompute
  18. 2026-06-23 00:30 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-52799?
CVE-2026-52799 is a high vulnerability published on June 22, 2026. Gogs 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 REQUIRESIGNINVIEW = false, we…
When was CVE-2026-52799 disclosed?
CVE-2026-52799 was first published in the National Vulnerability Database on June 22, 2026, with the most recent update on June 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-52799 actively exploited?
CVE-2026-52799 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 34.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-52799?
CVE-2026-52799 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-52799?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-52799, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-52799

Explore →

Is Your Infrastructure Affected by CVE-2026-52799?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs