CVE-2026-58443
published 2026-08-13CVE-2026-58443: Public-only repository tokens can update private PR head branches
PriorityP346critical9.1CVSS 3.1
AVNACLPRNUINSUCNIHAH
EPSS
0.58%
46.6th percentile
Public-only repository tokens can update private PR head branches
Affected
2 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| code.gitea.io | gitea | >= 0 < 1.27.0 | 1.27.0 |
| gitea | gitea_open_source_git_server | <= 1.26.4 | — |
CVSS provenance
nvdv3.19.1CRITICALCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H
vendor_redhat9.1CRITICAL
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Red Hat
code.gitea.io/gitea: Gitea: Unauthorized update of private pull request branches via public-only tokens
vendor_redhat·2026-08-13·CVSS 9.1
CVE-2026-58443 [CRITICAL] CWE-266 code.gitea.io/gitea: Gitea: Unauthorized update of private pull request branches via public-only tokens
code.gitea.io/gitea: Gitea: Unauthorized update of private pull request branches via public-only tokens
Public-only repository tokens can update private PR head branches
A flaw was found in Gitea. This vulnerability allows an attacker to use tokens intended for public repositories to modify private pull request (PR) branches. This could lead to unauthorized changes in private code, compromising the integrity of the affected repositories.
Statement: A flaw was found in Gitea where public-only repository tokens can be used to write to private pull request head branches. This authorization bypass allows an attacker with a valid public-only write:repository token to modify private repository branches through public base repository API endpoints, bypassing the public-only token restriction.
GHSA
Gitea: Public-only repository tokens can update private PR head branches
ghsa·2026-07-21
CVE-2026-58443 [CRITICAL] CWE-863 Gitea: Public-only repository tokens can update private PR head branches
Gitea: Public-only repository tokens can update private PR head branches
### Summary
Gitea allows a `public-only,write:repository` token to update a private pull request head branch through a public base repository route.
The vulnerable endpoint is:
```text
POST /api/v1/repos/{public-owner}/{public-repo}/pulls/{index}/update
```
Gitea checks the token's public-only restriction against the route repository, which is the public base repository. `UpdatePullRequest()` then authorizes the pull request head repository with ordinary user RBAC and calls the pull update service. If the head repository is private, the active token's public-only restriction is not re-applied to that private repository before Gitea pushes changes into it.
As a result, the same token that cannot directly write to
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2026-58443 code.gitea.io/gitea: Gitea: Unauthorized update of private pull request branches via public-only tokens
bugzilla·2026-08-13·CVSS 9.1
CVE-2026-58443 [CRITICAL] CVE-2026-58443 code.gitea.io/gitea: Gitea: Unauthorized update of private pull request branches via public-only tokens
CVE-2026-58443 code.gitea.io/gitea: Gitea: Unauthorized update of private pull request branches via public-only tokens
Public-only repository tokens can update private PR head branches
Hackernews
⚡ Weekly Recap: Rogue AI Models, $88M Bitcoin Theft, Water-System Attacks and Dangling DNS Hijacks
blogs_hackernews·2026-08-03
CVE-2026-42897 ⚡ Weekly Recap: Rogue AI Models, $88M Bitcoin Theft, Water-System Attacks and Dangling DNS Hijacks
Home
Threat Intelligence
Vulnerabilities
Cyber Attacks
Webinars
Expert Insights
Awards
Webinars
Awards
Free eBooks
About THN
Jobs
Advertise with us
## ⚡ Weekly Recap: Rogue AI Models, $88M Bitcoin Theft, Water-System Attacks and Dangling DNS Hijacks
This week kept coming back to permission. A model crossed a boundary. A wallet trusted bad randomness. Webmail kept an intruder around. Public systems, package feeds, hotel networks, and login flows all gave away more than intended.
Some of it was clever. Most of it was just access left lying around: old bugs, exposed gear, poisoned dependencies, weak defaults, and tooling that moved from forum chatter to real targets.
The full weekly recap report follows.
## ⚡ Threat of the Week
Anthropic Disclosed its Models Targeted 3 O
2026-08-13
Published