Private repository disclosure via persistent collaborator webhooks
Published Aug 13, 2026 · Updated Aug 13, 2026
Authorization failure in Gitea 1.26.4 and earlier allows remote authenticated users to receive private repository events after access revocation. DeleteCollaboration removes collaboration state but leaves collaborator-created webhooks active, while delivery does not recheck the creator's access. Exploitation requires prior admin collaborator access and webhook creation, after which future issue, comment, and commit data reaches the former collaborator.
Summary
What happened
Authorization failure in Gitea 1.26.4 and earlier allows remote authenticated users to receive private repository events after access revocation. DeleteCollaboration removes collaboration state but leaves collaborator-created webhooks active, while delivery does not recheck the creator's access. Exploitation requires prior admin collaborator access and webhook creation, after which future issue, comment, and commit data reaches the former collaborator.
The record
- CVE
- CVE-2026-58440
- Published
- Aug 13, 2026
- Updated
- Aug 13, 2026
- Vendor
- Gitea
- Product
- Gitea
- Classifications
- CWE-863, T1213.003
- Attack vector
- network
- Privileges
- admin
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.
Weakness, pattern, technique
Public exploit references
- Vendor-published webhook persistence reproductionfunctional · 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