Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-52813 – Path Traversal leading to RCE – Gogs prior to 0.14.3

Be the first to know when new zero-days emerge:

Summary

CVE-2026-52813 is a critical path traversal vulnerability (CWE-23) in Gogs, the open-source self-hosted Git service, affecting all versions prior to 0.14.3. Because Gogs fails to sanitize organization names before using them to construct filesystem paths, an attacker can write repository data to arbitrary locations on the server and overwrite Git hook scripts in other repositories, resulting in Remote Code Execution (RCE). The vulnerability carries a CVSS v3.1 base score of 10.0 (Critical).

Technical details

  • Root cause: The function os.MkdirAll(repox.UserPath(org.Name)) in internal/database/org.go passes the attacker-controlled organization name directly into a filesystem path construction without neutralizing directory traversal sequences (../). This allows repository directories to be created at arbitrary locations outside the intended data directory.
  • Trigger conditions: An attacker registers an organization with a crafted name containing path traversal sequences (e.g., ../../../../data/gogs/data/tmp/local-r/{ID}/nested) and creates a repository within it. This places the new repository’s directory structure inside the working tree of an existing, legitimate repository on the same server.
  • Attack vector: The attacker then modifies the nested repository’s hooks/update file to contain arbitrary shell commands. Any subsequent interaction that triggers the overwritten Git hook (such as a push to the target repository) causes those commands to execute as the git user.
  • Impact: Full Remote Code Execution as the git user — compromising all hosted repository data, configuration files, and potentially enabling further lateral movement within the host system. All three pillars of confidentiality, integrity, and availability are fully compromised (scored High/High/High with Changed scope).
  • Authentication: While the attack requires a registered Gogs user account, Gogs enables open self-registration by default, making this vulnerability effectively exploitable by any unauthenticated internet user on default-configured instances. NVD rates Privileges Required as None.

Affected software

  • Gogs — all versions prior to 0.14.3

Severity

  • CVSS v3.1 Base Score: 10.0 (Critical)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
  • CWE: CWE-23 (Relative Path Traversal)

Mitigation and recommended actions

  • Immediate action: Upgrade to Gogs 0.14.3 or later, which contains the vendor-provided fix (pull request #8334, commit f6acd46).
  • If immediate patching is not possible:
    • Restrict Gogs access to trusted internal networks and block public self-registration via the DISABLE_REGISTRATION setting in app.ini to eliminate unauthenticated exploitation paths.
    • Review existing organization names for any containing ../ sequences and remove or rename them immediately.
    • Monitor Git hook files across hosted repositories for unexpected modifications.

IONIX Status

The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge