← Back to results
Vulnerability record · public intelligence
CVE-2026-22592
MEDIUM

Gogs has a Denial of Service issue

Published Feb 6, 2026 · Updated Oct 23, 2026 · Also known as GO-2026-4451, GHSA-cr88-6mqm-4g57

Severity · CVSSMEDIUM · 6.5
Known exploitationNot listed
EPSS / likelihood0.38%
QFinch risk scoreNot available

Original summary

Normalized public record · Updated Oct 23, 2026

Gogs has a Denial of Service issue

Publisher and source text is retained separately from QFinch interpretation.

QFinch assessment

An authenticated user can cause a DOS attack. If one of the repo files is deleted before synchronization, it will cause the application to crash.

Potential impact

Denial of Service server crash.

Technical context

If GetMirrorByRepoID fails, the error log dereferencing null pointer. This happens if the repository no longer exits. https://github.com/gogs/gogs/blob/4cc83c498b6ae59356a04912d68a932165bad5e6/internal/database/mirror.goL333-L337 if err != nil m is alwasa nil https://github.com/gogs/gogs/blob/4cc83c498b6ae59356a04912d68a932165bad5e6/internal/database/mirror.goL269-L278

Evidence: public source records

Affected products

Affected scope reported by the available public evidence
Affected package, product or rangeFix status
Consult the referenced vendor advisory for affected versions.Consult source advisory

Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.

Remediation

Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.

  1. Confirm the affected product and reachable code path exist in your environment.
  2. Apply the vendor-supported patch or mitigation from the primary advisory.
  3. Rescan the exact deployed revision and retain verification evidence.
Review primary references

Evidence coverage

CVENVDOSVEPSSGHSA
SSVC priority
LOW
Confidence
Not available
Aliases
GO-2026-4451, GHSA-cr88-6mqm-4g57

Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.

Sources and record history

  1. Security advisory ↗

Record history

Published Feb 6, 2026 · Last refreshed Oct 23, 2026