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.
{
"cna_assigner": "Gitea",
"cwe_ids": [
"CWE-862"
],
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/129xxx/CVE-2026-129337.json"
}{
"extracted_events": [
{
"range": [
{
"introduced": "1.16.0"
},
{
"fixed": "28.4.0"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StandardRange"
},
{
"original_tag": "v28.4.0",
"range": [
{
"fixed": "0b5dfdeeeaadf6350314246c5936b53cce38170c"
}
],
"source": "REFERENCES_TAG"
}
]
}