Is CVE-2026-58434 exploited in the wild?

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

How severe is CVE-2026-58434?

Medium severity, with a CVSS score of 4, 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-58434?

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-58434 attacked?

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

Am I affected by CVE-2026-58434?

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-58434: Gitea information disclosure via starred repository metadata after access revocation

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-58434?

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-58434 attacked?

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

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

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-58434 · Severity: medium · CVSS 4 · Published 2026-07-21

Gitea is a self-hosted software development service similar to GitHub. A security issue was identified where users who previously had access to a private project could still see basic information about that project (like its name and description) even after their access was officially revoked. While this does not expose the actual source code or sensitive files, it allows unauthorized individuals to track the project's name and status changes.

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

Quick answers

Is CVE-2026-58434 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-58434 being exploited in the wild.
How severe is CVE-2026-58434?: Medium severity, with a CVSS score of 4, 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-58434?: 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-58434 attacked?: It is attacked over the network, in a hosted service.
Am I affected by CVE-2026-58434?: 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

An information disclosure vulnerability exists in Gitea's API due to missing authorization checks in the 'starred' and 'subscriptions' endpoints. When a user's access to a private repository is revoked, they are correctly blocked from direct repository access; however, if they had previously 'starred' or 'subscribed' to the repository, the metadata remains visible via `GET /api/v1/user/starred` and `GET /api/v1/user/subscriptions`. An authenticated attacker can view the repository's full name, description, and visibility status, including updates made to these fields after revocation. The vulnerability is fixed in version 1.27.0.

Affected products

Gitea Gitea < 1.27.0

Identifiers

CVE-2026-58434
GHSA-j2w3-9c3r-g83q
GO-2026-6062

Timeline

2026-07-13: disclosed: Initial disclosure to vendor
2026-07-21: advisory: GitHub Advisory published
2026-07-21: patched: Fix released in version 1.27.0

References

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