Is CVE-2026-26292 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-26292 being exploited in the wild.

How severe is CVE-2026-26292?

Critical severity, with a CVSS score of 9.8, published 3 July 2026.

Which products and versions are affected?

Gitea < 1.25.5; code.gitea.io/gitea (Go) < 1.25.5, SEMVER:introduced=0,fixed=1.25.5.

Is there a fix for CVE-2026-26292?

Yes. code.gitea.io/gitea (Go): upgrade to 1.25.5 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-26292 attacked?

It is attacked over the network, in a hosted service.

Am I affected by CVE-2026-26292?

Check whether you run Gitea or code.gitea.io/gitea (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-26292: Gitea migration transport bypass in LFS mirror operations

Q: Which products and versions are affected?

Gitea < 1.25.5; code.gitea.io/gitea (Go) < 1.25.5, SEMVER:introduced=0,fixed=1.25.5.

Q: Is there a fix for CVE-2026-26292?

Yes. code.gitea.io/gitea (Go): upgrade to 1.25.5 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-26292 attacked?

It is attacked over the network, in a hosted service.

Q: Am I affected by CVE-2026-26292?

Check whether you run Gitea or code.gitea.io/gitea (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-26292 · Severity: critical · CVSS 9.8 · Published 2026-07-03

Gitea is a self-hosted Git repository management platform that supports mirroring repositories from external sources. When administrators configure special network protections (such as authentication requirements, proxy rules, or certificate validation) for migrating repositories, those protections are intended to apply to all data transfers. However, Git Large File Storage (LFS) operations during mirror pushes and syncs were bypassing these protections, potentially allowing attackers to exfiltrate data or inject malicious content through unprotected channels.

Technologies: Gitea, code.gitea.io/gitea (Go). Vendors: Gitea, Go.

Quick answers

Is CVE-2026-26292 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-26292 being exploited in the wild.
How severe is CVE-2026-26292?: Critical severity, with a CVSS score of 9.8, published 3 July 2026.
Which products and versions are affected?: Gitea < 1.25.5; code.gitea.io/gitea (Go) < 1.25.5, SEMVER:introduced=0,fixed=1.25.5.
Is there a fix for CVE-2026-26292?: Yes. code.gitea.io/gitea (Go): upgrade to 1.25.5 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-26292 attacked?: It is attacked over the network, in a hosted service.
Am I affected by CVE-2026-26292?: Check whether you run Gitea or code.gitea.io/gitea (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

code.gitea.io/gitea (Go): upgrade to 1.25.5 or later
```
go get code.gitea.io/gitea@v1.25.5
```

Technical details

The vulnerability is an access control bypass (CWE-284) in Gitea's LFS mirror operations. The root cause is that LFS push and sync operations during mirror migrations were using the default HTTP client instead of the configured migration HTTP transport, which is designed to enforce authentication, proxy settings, and certificate validation policies. This affects all Gitea versions before 1.25.5. The attack vector is network-based and requires no privileges or user interaction—an attacker can exploit this by initiating a mirror operation that triggers LFS transfers. The impact is high across confidentiality, integrity, and availability: attackers can intercept or manipulate LFS data transfers, bypass security policies, and potentially access sensitive repository content. The fix, implemented in version 1.25.5, applies the migration HTTP transport configuration to LFS client operations during mirror push and sync operations.

Affected products

Gitea Gitea < 1.25.5

Identifiers

CVE-2026-26292
GHSA-rc56-rj3f-xggf
GO-2026-6344

Timeline

2026-07-03: disclosed: Published to GitHub Advisory Database and NVD
2026-03-16: patched: Fixed in Gitea 1.25.5 release

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.