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

New CVE Detected

CVE-2026-25718 – Symlink Traversal Leading to RCE – Gitea Open Source Git Server before 1.25.5

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

Summary

CVE-2026-25718 is a critical symlink-following path traversal vulnerability (CWE-59) in Gitea Open Source Git Server, affecting all versions prior to 1.25.5. The flaw resides in the template repository generation workflow, where path resolution fails to reject symlinked or non-regular filesystem paths, allowing an attacker to read or write arbitrary files on the underlying host — including injecting SSH keys to achieve remote code execution (RCE) as the git system user. With a CVSS 3.1 score of 9.1 (Critical) and a public proof-of-concept exploit available, unpatched internet-exposed Gitea instances are at immediate and material risk.

Technical details

  • Root cause: During template repository generation, Gitea’s path resolution logic (CWE-59: Improper Link Resolution Before File Access / ‘Link Following’) does not validate whether file paths resolve through symbolic links or to non-regular filesystem objects. The template engine operates on the dereferenced target rather than the intended repository content.
  • Trigger conditions: An attacker creates a malicious template repository containing a symlink targeting a sensitive file (e.g., the git user’s ~/.ssh/authorized_keys). A template variable such as ${REPO_DESCRIPTION} is embedded in the symlinked file’s content. When a new repository is created from this template with Git content templating enabled, the engine expands the variable using the attacker-controlled repository description — effectively writing an arbitrary string into the symlink target.
  • Attack vector: Network — exploitable entirely remotely. The public PoC demonstrates exploitation by a registered user account; on Gitea instances with open user registration (a common default for self-hosted community deployments), no elevated privileges are required to obtain an account and trigger the vulnerability.
  • Impact:
    • Arbitrary file write — injection of an attacker-controlled SSH public key into authorized_keys, granting interactive shell login as the git system user (full RCE).
    • Arbitrary file read — access to sensitive server-side files via the symlink dereference path.
    • Secondary impacts — corruption of Gitea configuration files, SQLite database manipulation, or denial of service through forced access to large files.

Affected software

  • Gitea Open Source Git Server: all versions before 1.25.5

Severity

CVSS v3.1 Base Score: 9.1 (Critical)
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Mitigation and recommended actions

  • Immediate: Upgrade to Gitea 1.25.5 or later. The fix was introduced via pull requests #36734 and #36746, correcting path resolution handling during template repository generation.
  • If immediate patching is not feasible:
    • Restrict network access to the Gitea web interface using firewall rules or a reverse proxy with IP allowlisting.
    • Disable open/public user registration to prevent unauthenticated actors from obtaining accounts.
    • Disable or restrict the use of template repositories until patching is complete.

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