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

Back
New CVE Detected

CVE-2026-26292 – SSRF via LFS Migration Transport Bypass – Gitea before 1.25.5

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

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-26292 is a critical Server-Side Request Forgery (SSRF) vulnerability affecting Gitea Open Source Git Server in all versions prior to 1.25.5. The flaw arises because LFS (Large File Storage) push and sync mirror operations do not use the migration HTTP transport layer, thereby bypassing the configured migration transport SSRF protections for those LFS requests. With a CVSS v3.1 score of 9.8 (Critical), this vulnerability allows attackers to coerce the Gitea server into issuing arbitrary HTTP requests to internal network addresses, cloud metadata endpoints, or otherwise unreachable internal APIs.

Technical details

  • Root cause: LFS push and sync mirror operations in Gitea versions before 1.25.5 fail to route through the migration HTTP transport. The migration transport is the designated layer that enforces SSRF protections for outbound HTTP requests; by bypassing it entirely, LFS operations are subject to no such restrictions.
  • Trigger conditions: An attacker can trigger this bypass by initiating LFS push or sync mirror operations against a target Gitea instance. The NVD rates this as requiring no privileges (PR:N), consistent with open-registration Gitea deployments where any user can initiate LFS-enabled repository operations.
  • Attack vector: Network-accessible (AV:N). Gitea is widely deployed as an internet-facing self-hosted Git service, making exposed instances directly reachable.
  • Impact: By crafting LFS requests targeting internal addresses, an attacker can perform internal port scanning, access cloud instance metadata endpoints (e.g., AWS IMDSv1 at 169.254.169.254), and interact with internal APIs from the Gitea server’s network context — resulting in high confidentiality, integrity, and availability impact as assessed by NVD.

Affected software

  • Gitea Open Source Git Server — all versions before 1.25.5

Severity

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

Mitigation and recommended actions

  • Immediate: Upgrade Gitea to version 1.25.5 or later. This release introduces migration HTTP transport support for LFS push and sync mirror operations (via patches in PRs #36665 and #36691), closing the bypass.
  • If immediate patching is not feasible: Restrict network-level access to the Gitea instance so that it cannot make outbound requests to internal network ranges or cloud metadata endpoints. Enforce egress filtering at the network perimeter to block the Gitea server from reaching 169.254.169.254 and RFC 1918 address space.

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

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

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

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

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

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge