CVE-2026-52810

HIGHPre-NVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 74% 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.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.1Exploit: None knownExposed: 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, Git smart HTTP authorizes POST …/git-receive-pack using the client-supplied service query string (so ?service=git-upload-pack is evaluated as read access) while routing still runs git receive-pack, allowing push where only read should be allowed. This vulnerability is fixed in 0.14.3.

CVSS v3
7.1
EG Score
7.1(medium)
EG Risk
37(Track)
EG Risk 37/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity71% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
26%
KEV
Not listed

Published

June 23, 2026

Last Modified

June 25, 2026

Advisory Details (4)

Auto-updated Jun 24, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_pr, github_release, github.
github Patch Available🟡 PoC Available

Write to readonly repositories using receive-pack + service=git-upload-pack confusion · Advisory · gogs/gogs · GitHub

https://github.com/gogs/gogs/security/advisories/GHSA-wmfg-5p4h-5fw3
github_release Patch Available

0.14.3

Patch available: gogs/gogs v0.14.3

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

security: authorize Git HTTP by routed action, not client-supplied service

Fix merged in gogs/gogs PR #8331 on 2026-06-07 — awaiting tagged release

https://github.com/gogs/gogs/pull/8331
github_commit

commit 7c9cf53aca95 (gogs/gogs)

Fix landed in gogs/gogs commit 7c9cf53aca95 — awaiting tagged release

https://github.com/gogs/gogs/commit/7c9cf53aca957959bcd98b0cc987d9901b7cb184

Vendor Advisories for CVE-2026-52810(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———

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× 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-26 15:54 UTCEG score recompute
  2. 2026-07-26 14:54 UTCEPSS rescore
  3. 2026-07-25 14:18 UTCEPSS rescore
  4. 2026-07-24 14:18 UTCEPSS rescore
  5. 2026-07-23 14:18 UTCEPSS rescore
  6. 2026-07-23 03:19 UTCEG score recompute
  7. 2026-07-22 14:08 UTCEPSS rescore
  8. 2026-07-21 15:25 UTCEPSS rescore
  9. 2026-07-20 17:08 UTCEPSS rescore
  10. 2026-07-19 14:31 UTCEPSS rescore
  11. 2026-07-19 14:31 UTCEPSS rescore
  12. 2026-07-19 02:29 UTCEPSS rescore
  13. 2026-07-18 10:04 UTCEPSS rescore
  14. 2026-07-16 17:03 UTCEPSS rescore
  15. 2026-07-15 16:57 UTCEPSS rescore
  16. 2026-07-15 16:57 UTCEPSS rescore
  17. 2026-07-15 02:00 UTCEPSS rescore
  18. 2026-07-15 02:00 UTCEPSS rescore
  19. 2026-07-13 22:31 UTCEPSS rescore
  20. 2026-07-13 06:13 UTCEPSS rescore
  21. 2026-07-13 06:13 UTCEPSS rescore
  22. 2026-07-12 05:46 UTCEPSS rescore
  23. 2026-07-11 08:27 UTCEPSS rescore
  24. 2026-07-11 08:27 UTCEPSS rescore
  25. 2026-07-09 19:10 UTCEPSS rescore
Show 23 more
  1. 2026-07-09 19:10 UTCEPSS rescore
  2. 2026-07-08 15:16 UTCEPSS rescore
  3. 2026-07-08 15:16 UTCEPSS rescore
  4. 2026-07-07 13:46 UTCEPSS rescore
  5. 2026-07-07 13:46 UTCEPSS rescore
  6. 2026-07-06 16:27 UTCEPSS rescore
  7. 2026-07-06 16:27 UTCEPSS rescore
  8. 2026-07-06 02:23 UTCEPSS rescore
  9. 2026-07-06 02:23 UTCEPSS rescore
  10. 2026-07-05 02:30 UTCEPSS rescore
  11. 2026-07-04 06:31 UTCEPSS rescore
  12. 2026-07-01 15:07 UTCEPSS rescore
  13. 2026-06-30 23:22 UTCEPSS rescore
  14. 2026-06-29 14:06 UTCEPSS rescore
  15. 2026-06-29 14:06 UTCEPSS rescore
  16. 2026-06-28 14:07 UTCEPSS rescore
  17. 2026-06-28 04:56 UTCEPSS rescore
  18. 2026-06-28 04:56 UTCEPSS rescore
  19. 2026-06-27 03:08 UTCEPSS rescore
  20. 2026-06-25 13:49 UTCEPSS rescore
  21. 2026-06-24 22:04 UTCEG score recompute▲ 7.10
  22. 2026-06-24 22:03 UTCNVD updateCVSS v3 → 7.1 · CVSS v4 → 7.1
  23. 2026-06-23 17:21 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-52810?
CVE-2026-52810 is a high vulnerability published on June 23, 2026. Gogs is an open source self-hosted Git service. Prior to 0.14.3, Git smart HTTP authorizes POST …/git-receive-pack using the client-supplied service query string (so ?service=git-upload-pack is evaluated as read access) while routing still runs git receive-pack, allowing push where only read should…
When was CVE-2026-52810 disclosed?
CVE-2026-52810 was first published in the National Vulnerability Database on June 23, 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-52810 actively exploited?
CVE-2026-52810 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 73.8% of all scored CVEs.
What is the CVSS score of CVE-2026-52810?
CVE-2026-52810 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-52810?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-52810, 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-52810

Explore →

Is Your Infrastructure Affected by CVE-2026-52810?

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

Start Free Scan →Browse All CVEs