CVE-2026-52806

CRITICALPre-NVD 9.99.9
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 1.0%, top 40% 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
Elevated
9.9
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 9.9Exploit: 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, Gogs allows authenticated users to achieve Remote Code Execution (RCE) on the server by creating a pull request with a specially crafted branch name that injects the --exec flag into the git rebase command during the "Rebase before merging" merge operation. This vulnerability is fixed in 0.14.3.

CVSS v3
9.9
EG Score
9.9(medium)
EPSS
59.5%
KEV
Not listed

Published

June 23, 2026

Last Modified

June 26, 2026

Advisory Details (4)

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

RCE via git rebase --exec argument injection in pull request merge · Advisory · gogs/gogs · GitHub

https://github.com/gogs/gogs/security/advisories/GHSA-qf6p-p7ww-cwr9
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: fix argument injection in pull request merge (rebase)

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

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

commit a9dbafbfd8e1 (gogs/gogs)

Fix landed in gogs/gogs commit a9dbafbfd8e1 — awaiting tagged release

https://github.com/gogs/gogs/commit/a9dbafbfd8e1020bacc626420238c01d75d03364

Vendor Advisories for CVE-2026-52806(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 47× in last 7d / 89× 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 03:06 UTCEG score recompute
  2. 2026-07-06 22:53 UTCEG score recompute
  3. 2026-07-06 18:42 UTCEG score recompute
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 16:27 UTCEPSS rescore
  6. 2026-07-06 13:59 UTCEG score recompute
  7. 2026-07-06 09:48 UTCEG score recompute
  8. 2026-07-06 05:36 UTCEG score recompute
  9. 2026-07-06 02:23 UTCEPSS rescore
  10. 2026-07-06 01:26 UTCEG score recompute
  11. 2026-07-05 21:16 UTCEG score recompute
  12. 2026-07-05 17:06 UTCEG score recompute
  13. 2026-07-05 12:53 UTCEG score recompute
  14. 2026-07-05 08:41 UTCEG score recompute
  15. 2026-07-05 04:31 UTCEG score recompute
  16. 2026-07-05 02:30 UTCEPSS rescore
  17. 2026-07-05 00:13 UTCEG score recompute
  18. 2026-07-04 20:01 UTCEG score recompute
  19. 2026-07-04 15:50 UTCEG score recompute
  20. 2026-07-04 11:40 UTCEG score recompute
  21. 2026-07-04 07:30 UTCEG score recompute
  22. 2026-07-04 06:31 UTCEPSS rescore
  23. 2026-07-04 02:59 UTCEG score recompute
  24. 2026-07-03 22:41 UTCEG score recompute
  25. 2026-07-03 18:31 UTCEG score recompute
Show 64 more
  1. 2026-07-03 14:20 UTCEG score recompute
  2. 2026-07-03 10:11 UTCEG score recompute
  3. 2026-07-03 06:00 UTCEG score recompute
  4. 2026-07-03 01:49 UTCEG score recompute
  5. 2026-07-02 21:39 UTCEG score recompute
  6. 2026-07-02 17:30 UTCEG score recompute
  7. 2026-07-02 13:18 UTCEG score recompute
  8. 2026-07-02 09:08 UTCEG score recompute
  9. 2026-07-02 04:59 UTCEG score recompute
  10. 2026-07-02 00:49 UTCEG score recompute
  11. 2026-07-01 20:40 UTCEG score recompute
  12. 2026-07-01 16:30 UTCEG score recompute
  13. 2026-07-01 15:07 UTCEPSS rescore
  14. 2026-07-01 12:18 UTCEG score recompute
  15. 2026-07-01 08:06 UTCEG score recompute
  16. 2026-07-01 03:56 UTCEG score recompute
  17. 2026-06-30 23:46 UTCEG score recompute
  18. 2026-06-30 23:22 UTCEPSS rescore
  19. 2026-06-30 19:22 UTCEG score recompute
  20. 2026-06-30 15:12 UTCEG score recompute
  21. 2026-06-30 10:57 UTCEG score recompute
  22. 2026-06-30 06:45 UTCEG score recompute
  23. 2026-06-30 02:34 UTCEG score recompute
  24. 2026-06-29 22:24 UTCEG score recompute
  25. 2026-06-29 18:15 UTCEG score recompute
  26. 2026-06-29 14:04 UTCEG score recompute
  27. 2026-06-29 09:54 UTCEG score recompute
  28. 2026-06-29 05:44 UTCEG score recompute
  29. 2026-06-29 01:32 UTCEG score recompute
  30. 2026-06-28 21:22 UTCEG score recompute
  31. 2026-06-28 17:13 UTCEG score recompute
  32. 2026-06-28 14:07 UTCEPSS rescore
  33. 2026-06-28 13:02 UTCEG score recompute
  34. 2026-06-28 08:53 UTCEG score recompute
  35. 2026-06-28 04:56 UTCEPSS rescore
  36. 2026-06-28 04:56 UTCEPSS rescore
  37. 2026-06-28 04:44 UTCEG score recompute
  38. 2026-06-28 00:34 UTCEG score recompute
  39. 2026-06-27 20:24 UTCEG score recompute
  40. 2026-06-27 16:14 UTCEG score recompute
  41. 2026-06-27 12:04 UTCEG score recompute
  42. 2026-06-27 07:55 UTCEG score recompute
  43. 2026-06-27 03:45 UTCEG score recompute
  44. 2026-06-27 03:08 UTCEPSS rescore
  45. 2026-06-26 23:35 UTCEG score recompute
  46. 2026-06-26 19:25 UTCEG score recompute
  47. 2026-06-26 15:15 UTCEG score recompute
  48. 2026-06-26 11:05 UTCEG score recompute
  49. 2026-06-26 04:39 UTCEG score recompute
  50. 2026-06-26 00:28 UTCEG score recompute
  51. 2026-06-25 20:18 UTCEG score recompute
  52. 2026-06-25 16:08 UTCEG score recompute
  53. 2026-06-25 13:49 UTCEPSS rescore
  54. 2026-06-25 11:58 UTCEG score recompute
  55. 2026-06-25 07:49 UTCEG score recompute
  56. 2026-06-25 03:39 UTCEG score recompute
  57. 2026-06-24 23:29 UTCEG score recompute
  58. 2026-06-24 19:19 UTCEG score recompute
  59. 2026-06-24 14:19 UTCEG score recompute
  60. 2026-06-24 10:10 UTCEG score recompute
  61. 2026-06-24 05:58 UTCEG score recompute
  62. 2026-06-24 01:43 UTCEG score recompute
  63. 2026-06-23 21:33 UTCEG score recompute
  64. 2026-06-23 17:22 UTCEG score recompute

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCportbuster1337/CVE-2026-52806
    First seen May 28, 2026

    Gogs RCE via argument injection in git rebase (CWE-88) — Python PoC. CVE-2026-52806

    Open source ↗

Frequently asked(5)

What is CVE-2026-52806?
CVE-2026-52806 is a critical vulnerability published on June 23, 2026. Gogs is an open source self-hosted Git service. Prior to 0.14.3, Gogs allows authenticated users to achieve Remote Code Execution (RCE) on the server by creating a pull request with a specially crafted branch name that injects the --exec flag into the git rebase command during the "Rebase before…
When was CVE-2026-52806 disclosed?
CVE-2026-52806 was first published in the National Vulnerability Database on June 23, 2026, with the most recent update on June 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-52806 actively exploited?
CVE-2026-52806 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 59.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-52806?
CVE-2026-52806 has a CVSS v3 base score of 9.9 (NVD).
How do I remediate CVE-2026-52806?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-52806, 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

Explore the affected products and dependency analysis for CVE-2026-52806

Explore →

Is Your Infrastructure Affected by CVE-2026-52806?

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