# CVE-2026-129337 — Gitea

> As of 2026-11-15, CVE-2026-129337 is a vulnerability in Gitea, EPSS 0.1% (4.1th percentile). No Threadlinqs-tracked threat campaign has been attributed to CVE-2026-129337 as of 2026-11-15; the identifier is re-checked against the Threadlinqs threat corpus on every daily ingest.

**Last updated:** 2026-11-15

## What is CVE-2026-129337?

Git over HTTP lowers the required permission for pushes to read access, so that the AGit flow works, and relies on the repository's server-side hooks to enforce write access. A repository that is still being created by a migration, fork or template generation has no hooks yet, so a user with read access to it could push branches and tags during that window, or after a failed migration that left the repository in that state. Git over HTTP now refuses requests to repositories that are still being created.

The record classifies CVE-2026-129337 under weakness class [CWE-862](https://intel.threadlinqs.com/cwe/CWE-862). 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 4 days ago.

## Severity and exploitation probability

- **EPSS (FIRST):** 0.1% probability of exploitation in the next 30 days, higher than 4.1% of all scored CVEs
- **CISA KEV:** Not listed in the CISA Known Exploited Vulnerabilities catalog
- **Threadlinqs priority:** 0.2/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- **Published:** 2026-11-15

## Is CVE-2026-129337 being exploited?

It currently carries a trending score of 31 in the Threadlinqs vulnerability feed.

## Affected products and versions

- [Gitea](https://intel.threadlinqs.com/vendors/gitea): Gitea

## How to fix CVE-2026-129337

Patch reference: [https://github.com/go-gitea/gitea/pull/40120](https://github.com/go-gitea/gitea/pull/40120). Vendor advisory: [https://github.com/go-gitea/gitea/security/advisories/GHSA-8cjj-9p56-j54f](https://github.com/go-gitea/gitea/security/advisories/GHSA-8cjj-9p56-j54f). Apply the vendor fix referenced above to every affected product listed in this record, then confirm the running version against the vendor advisory.

## Threat activity tracking CVE-2026-129337

No threat campaign in the Threadlinqs corpus currently references CVE-2026-129337, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.

## Sources

Enriched from CVE.org, NVD, FIRST EPSS. This product uses the NVD API but is not endorsed or certified by the NVD.

**Vendor advisory and patch**

- [github.com — vendor advisory](https://github.com/go-gitea/gitea/security/advisories/GHSA-8cjj-9p56-j54f)
- [github.com — patch](https://github.com/go-gitea/gitea/pull/40120)
- [github.com — patch (40268)](https://github.com/go-gitea/gitea/pull/40268)
- [blog.gitea.com — release notes](https://blog.gitea.com/release-of-28.4.0/)
- [github.com — release notes](https://github.com/go-gitea/gitea/releases/tag/v28.4.0)

Canonical: https://intel.threadlinqs.com/cve/CVE-2026-129337
No Threadlinqs detection currently covers CVE-2026-129337; it is re-checked on every ingest.
Indicator values unlock with TL Creds (https://threadlinqs.com/tl-creds); MCP access for AI agents needs Purple: https://intel.threadlinqs.com/mcp
