Is CVE-2026-58437 exploited in the wild?

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

How severe is CVE-2026-58437?

High severity, with a CVSS score of 7.1, published 21 July 2026.

Which products and versions are affected?

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

Is there a fix for CVE-2026-58437?

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

How is CVE-2026-58437 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-58437?

Check whether you run Gitea, code.gitea.io/gitea (Go) or gitea.dev (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-58437: Gitea repository visibility manipulation via Git push options

Q: Which products and versions are affected?

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

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

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

Q: How is CVE-2026-58437 attacked?

It is attacked over the network, in a network appliance.

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

Check whether you run Gitea, code.gitea.io/gitea (Go) or gitea.dev (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-58437 · Severity: high · CVSS 7.1 · Published 2026-07-21

Gitea is an open-source self-hosted Git service used by organizations to manage source code. A vulnerability in its Git push handler allows users with administrative access to a specific repository to silently change its visibility from private to public or modify its template status. Because this action bypasses standard logging and notification systems, an insider could expose proprietary code or sensitive configuration files without leaving an audit trail or alerting other administrators.

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

Quick answers

Is CVE-2026-58437 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-58437 being exploited in the wild.
How severe is CVE-2026-58437?: High severity, with a CVSS score of 7.1, published 21 July 2026.
Which products and versions are affected?: Gitea < 1.27.0; code.gitea.io/gitea (Go) < 1.27.0, SEMVER:introduced=0,fixed=1.27.0; gitea.dev (Go) SEMVER:introduced=0,fixed=1.27.0.
Is there a fix for CVE-2026-58437?: Yes. code.gitea.io/gitea (Go): upgrade to 1.27.0 or later; gitea.dev (Go): upgrade to 1.27.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-58437 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-58437?: Check whether you run Gitea, code.gitea.io/gitea (Go) or gitea.dev (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.27.0 or later
```
go get code.gitea.io/gitea@v1.27.0
```
gitea.dev (Go): upgrade to 1.27.0 or later
```
go get gitea.dev@v1.27.0
```

Technical details

The vulnerability exists in the `HookPostReceive` function within `routers/private/hook_post_receive.go`. Gitea processes undocumented Git push options (`repo.private` and `repo.template`) using the `-o` flag during a `git push`. While intended for 'push-to-create' workflows, these options are processed for existing repositories without triggering the standard repository service logic. Consequently, changes to visibility or template status bypass the activity log, webhook events, and the `updated_at` timestamp update due to the use of `UpdateRepositoryColsNoAutoTime`. An attacker with admin-collaborator or owner permissions can use this to exfiltrate data or perform supply-chain attacks by silently toggling template designations. The issue is fixed in version 1.27.0.

Affected products

Gitea Gitea < 1.27.0

Identifiers

CVE-2026-58437
GHSA-8p9h-49rc-qgxj
GO-2026-6047

Timeline

2026-07-13: patched: Fixed in version 1.27.0
2026-07-21: advisory: GitHub Advisory published

References

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