Private branch writes via mis-scoped token check
Published Aug 13, 2026 · Updated Aug 13, 2026
Incorrect authorization in Gitea 1.26.4 and earlier allows remote authenticated users to write to private pull-request head branches. The update-pull-request API checks a public-only token against the public base repository, then pushes into the private head without reapplying that restriction. Exploitation requires a public-only token whose user can write the private head and a qualifying public-base pull request; the push can trigger private Actions workflows.
Summary
What happened
Incorrect authorization in Gitea 1.26.4 and earlier allows remote authenticated users to write to private pull-request head branches. The update-pull-request API checks a public-only token against the public base repository, then pushes into the private head without reapplying that restriction. Exploitation requires a public-only token whose user can write the private head and a qualifying public-base pull request; the push can trigger private Actions workflows.
The record
- CVE
- CVE-2026-58443
- Published
- Aug 13, 2026
- Updated
- Aug 13, 2026
- Vendor
- Gitea
- Product
- Gitea
- Classifications
- CWE-863, T1565.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 13, 2026CVE publishedPublication date reported by the CVE source.
- Aug 13, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=1.26.4
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- Upstream private-head update proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo