CVE-2026-22592

6.5 MEDIUM

📋 TL;DR

This vulnerability in Gogs allows authenticated users to cause a denial-of-service (DoS) attack by deleting repository files before synchronization, which crashes the application. It affects self-hosted Gogs instances running version 0.13.3 or earlier. Only authenticated users can exploit this vulnerability.

💻 Affected Systems

Products:
  • Gogs
Versions: 0.13.3 and prior
Operating Systems: All platforms running Gogs
Default Config Vulnerable: ⚠️ Yes
Notes: All Gogs installations with the affected versions are vulnerable regardless of configuration.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Malicious authenticated user crashes the Gogs service, causing complete unavailability for all users until manual restart.

🟠

Likely Case

Accidental or intentional deletion of repository files during synchronization causes service crashes and intermittent downtime.

🟢

If Mitigated

With proper access controls and monitoring, impact is limited to temporary service disruption that can be quickly detected and restored.

🌐 Internet-Facing: MEDIUM - Internet-facing instances are vulnerable to DoS attacks from authenticated malicious users.
🏢 Internal Only: MEDIUM - Internal instances remain vulnerable to both accidental and intentional exploitation by authenticated users.

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ✅ No
Complexity: LOW

Exploitation requires authenticated access to Gogs and knowledge of repository file deletion timing relative to synchronization processes.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 0.13.4 or 0.14.0+dev

Vendor Advisory: https://github.com/gogs/gogs/security/advisories/GHSA-cr88-6mqm-4g57

Restart Required: Yes

Instructions:

1. Backup your Gogs data and configuration. 2. Stop the Gogs service. 3. Upgrade to version 0.13.4 or later. 4. Restart the Gogs service. 5. Verify the service is running correctly.

🔧 Temporary Workarounds

Restrict repository file deletion permissions

all

Limit which authenticated users can delete repository files to reduce attack surface.

Configure Gogs repository permissions to restrict delete operations to trusted administrators only

🧯 If You Can't Patch

  • Implement strict access controls to limit which users can delete repository files
  • Monitor for service crashes and implement automated restart mechanisms

🔍 How to Verify

Check if Vulnerable:

Check Gogs version via web interface admin panel or by examining the binary/installation directory

Check Version:

gogs --version or check web interface at /admin

Verify Fix Applied:

Confirm version is 0.13.4 or later and test repository file deletion during synchronization

📡 Detection & Monitoring

Log Indicators:

  • Unexpected Gogs service crashes
  • Error logs related to file synchronization failures
  • Panic or segmentation fault messages in system logs

Network Indicators:

  • Sudden loss of connectivity to Gogs service
  • HTTP 5xx errors from Gogs endpoints

SIEM Query:

source="gogs.log" AND ("panic" OR "crash" OR "segmentation fault") OR source="system.log" AND process="gogs" AND ("terminated" OR "killed")

🔗 References

📤 Share & Export