What is the CVSS score of CVE-2026-26194?

CVE-2026-26194 has a CVSS 3.1 base score of 7.3 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:H/A:H. EPSS exploitation probability: 0.0%.

Is there a public PoC exploit available for CVE-2026-26194?

Yes, a public proof-of-concept exploit is available for CVE-2026-26194. Prioritise patching immediately. EPSS: 0.0%.

How to fix or mitigate CVE-2026-26194?

Within 24 hours: Inventory all Gogs instances and identify those running versions prior to 0.14.2; assess exposure by reviewing access logs for suspicious release deletion activity. Within 7 days: Apply the vendor patch to upgrade all Gogs installations to version 0.14.2 or later; test in non-production environments first. Within 30 days: Conduct post-patch validation, review git operation logs for signs of prior exploitation, and implement change management procedures to prevent future version drift.

Gogs CVE-2026-26194

HIGH

Improper Neutralization of Argument Delimiters in a Command ('Argument Injection') (CWE-88)

2026-03-05 security-advisories@github.com

GHSA-v9vm-r24h-6rqm

Code Injection Gogs Suse

7.3

CVSS 3.1 · GitHub Advisory

View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

Access

Authenticated user creates malicious release tag
Delivery

User triggers release deletion
Exploit

Unsanitized tag passed to git command
Execution

Git option injection occurs
Impact

Arbitrary git operations executed

Vulnerability Assessment

Weakness	CWE CWE-88 OWASP Top 10:2025 A05:2025 - Injection ASVS 5.0 V1 - Encoding and Sanitization Argument sanitization
Exploitation Conditions	Gogs version prior to 0.14.2 with release deletion functionality. Requires authenticated user account (PR:L) and user interaction to trigger deletion (UI:R). Git command injection via unsanitized tag name parameter in release deletion process.
Impact	CVSS 7.3 (HIGH). Attack vector: Network. Complexity: Low. Privileges required: Low. User interaction: Required. Public exploit/POC available.
Exploit ScenarioDerived	An attacker could exploit this vulnerability to compromise the affected system.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).

Patch available 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Mar 12, 2026

Gogs prior to version 0.14.2 contains a command injection vulnerability in release deletion functionality where improper handling of user-controlled tag names allows git options to be injected into git commands. An authenticated attacker with UI interaction can exploit this to achieve integrity and availability impacts. Public exploit code exists for this vulnerability.

Earlier versions of this analysis (1)

v1 Mar 12, 2026 - 22:06 CVSS 7.3

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. [CVSS 7.3 HIGH]

RemediationAI

A vendor patch is available — apply it immediately. Fixed in version 0.14.2.. Restrict network access to the affected service where possible.

Affected Packages

go gogs.io/gogs fix: 0.14.2

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in go

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

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

Know when Gogs gets its next vulnerability

Watch products and get an email when something new is published
Check this CVE against your own stack and servers
Exploit and PoC references, threat intelligence from 22 sources

Continue with Google Continue with GitHub

No credit card · 7-day full trial

Severity by source

GitHub Advisory PRIMARY 7.3 HIGH

AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:H/A:H

SUSE HIGH

Primary rating from GitHub Advisory.

CVSS VectorGitHub Advisory

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

Required

Scope

Unchanged

Confidentiality

None

Integrity

High

Availability

High

Lifecycle Timeline

PoC Detected

Mar 06, 2026 - 13:55 vuln.today

Public exploit code

Patch released

Mar 06, 2026 - 13:55 nvd

Patch available

CVE Published

Mar 05, 2026 - 19:16 nvd

HIGH 7.3

DescriptionGitHub Advisory

Executive ViewAI

Why It Matters

Gogs self-hosted Git service instances prior to version 0.14.2 contain a command injection vulnerability that allows attackers to execute arbitrary git operations by manipulating release tag names. Organizations running vulnerable Gogs deployments face potential data compromise, service disruption, and unauthorized code repository access if exploited.

Business Impact: High

Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score

0.0%

Top 89% exploitable

Exploit

POC

Public exploit code exists

Data Quality

4 sources

Confidence: Medium

NVD

CVE.org

EPSS Vendor

GitHub

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue

Severity HIGH

CISA KEV No

Public POC Yes

EPSS 0.0%

Patch available Yes

Active threat No

Deciding rule

HIGH severity (CVSS 7.0-8.9)

What every action level means

Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.

Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.

This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.

This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.

Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived

Scheduled

Exploitation· derived

Poc

System Exposure· derived

Open

Automatable· derived

Human Impact

High

Priority Score

Low Medium High Critical

KEV: 0

EPSS: 0

CVSS: +36

PoC: +20

Weaponized: 0

Threat intel: 0

Gov advisory: 0

Attack Technique

Code Injection CRITICAL

Code injection occurs when an application accepts user input and passes it directly into a language interpreter or evaluator without proper sanitization.