Private commit disclosure via stale fork authorization
Published Jul 3, 2026 · Updated Jul 3, 2026
Improper access control in Gitea 1.26.2 allows remote authenticated users to read private parent-repository commits through fork sync. The merge-upstream endpoint reuses a fork's parent link without checking whether the parent repository remains readable before importing new commits. The user must own a fork created while the parent was public; synchronization exposes only later parent commits and cannot modify the parent or reach never-forked repositories.
Summary
What happened
Improper access control in Gitea 1.26.2 allows remote authenticated users to read private parent-repository commits through fork sync. The merge-upstream endpoint reuses a fork's parent link without checking whether the parent repository remains readable before importing new commits. The user must own a fork created while the parent was public; synchronization exposes only later parent commits and cannot modify the parent or reach never-forked repositories.
The record
- CVE
- CVE-2026-24451
- Published
- Jul 3, 2026
- Updated
- Jul 3, 2026
- Vendor
- Gitea
- Product
- Gitea
- Classifications
- CWE-200, CWE-284, T1213.003
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 3, 2026CVE publishedPublication date reported by the CVE source.
- Jul 3, 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=1.26.2
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.
Weakness, pattern, technique
Public exploit references
- Gitea merge-upstream end-to-end proof of conceptfunctional · 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