Gogs is an open source self-hosted Git service. Prior to version 0.14.2, there's a security issue in gogs where deleting a release can fail if a user controlled tag name is passed to git without the right separator, this lets git options get injected and mess with the process. This issue has been patched in version 0.14.2.
CVE-2026-26194
This high-severity CVE scores 7.3 under NVD CVSS v3. EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). 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).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.3
- EG Score
- 7.3(low)
- 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 computedSeverity73% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 1%
- EPSS %ILE
- 41%
- KEV
- Not listed
Published
March 5, 2026
Last Modified
June 17, 2026
References (4)
- security-advisories@githubhttps://github.com/gogs/gogs/commit/a000f0c7a632ada40e6829abdeea525db4c0fc2d
- security-advisories@githubhttps://github.com/gogs/gogs/pull/8175
- security-advisories@githubhttps://github.com/gogs/gogs/releases/tag/v0.14.2
- security-advisories@githubhttps://github.com/gogs/gogs/security/advisories/GHSA-v9vm-r24h-6rqm
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 1× in last 7d / 1× 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.
- 2026-07-27 13:51 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-88
- CVE-2007-0882EG 10.0EPSS p100HIGH
- CVE-2004-0480EG 10.0EPSS p95HIGH
- CVE-1999-0113EG 10.0EPSS p97HIGH
- CVE-2018-3856EG 9.9CRITICAL
- CVE-2020-28026EG 9.8EPSS p95CRITICAL
- CVE-2020-21224EG 9.8EPSS p98CRITICAL
- CVE-2020-25494EG 9.8EPSS p98CRITICAL
- CVE-2020-15692EG 9.8EPSS p90CRITICAL
- CVE-2020-12641EG 9.8 KEVEPSS p100CRITICAL
- CVE-2019-12148EG 9.8CRITICAL
Frequently asked(5)
What is CVE-2026-26194?
When was CVE-2026-26194 disclosed?
Is CVE-2026-26194 actively exploited?
What is the CVSS score of CVE-2026-26194?
How do I remediate CVE-2026-26194?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-26194
Is Your Infrastructure Affected by CVE-2026-26194?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.