Quick answers
- Is CVE-2026-97208 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-97208 being exploited in the wild.
- How severe is CVE-2026-97208?
- Informational severity, published 6 October 2026.
- Which products and versions are affected?
- Gitea before 28.1.0.
- Is there a fix for CVE-2026-97208?
- Yes: fixed in Gitea 28.1.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-97208 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-97208?
- Check whether you run Gitea 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
- Fixed in: Gitea 28.1.0
Technical details
The POST `/api/v1/repos/{owner}/{repo}/push_mirrors` API endpoint checked only whether mirroring was enabled globally but failed to verify the `[mirror] DISABLE_NEW_PUSH` configuration setting that the web interface enforces. This is an authorization check bypass where a repository administrator (a user with elevated privileges within a repo but not site-wide admin) could circumvent site-level policy. The vulnerability requires authentication and repository admin privileges; the fix validates the caller's permission against the site configuration before allowing mirror creation.
Affected products
- Gitea Gitea before 28.1.0
Timeline
- 2026-10-06: disclosed
- 2026-10-06: patched