Gitea.dev: Gitea: Webhooks created by a collaborator keep firing after their repo access is revoked → ongoing real-time exfiltration of private repo content (CVE-2026-58440)
Gitea versions prior to 1.27.0 have a vulnerability where webhooks created by a collaborator with admin permissions on a private repository continue to fire even after that collaborator's access is revoked. The webhook delivery mechanism does not re-validate the creator's current access, allowing the former collaborator to receive full payloads of repository events indefinitely. This results in ongoing, invisible exfiltration of private repository content.
AI Analysis
Technical Summary
In Gitea (before version 1.27.0), when an admin collaborator creates a webhook on a private repository and later has their access revoked, the webhook remains active and continues to deliver event payloads to the former collaborator's endpoint. The function responsible for revoking collaboration access, DeleteCollaboration(), cleans watches and assignees but does not remove or disable webhooks created by the revoked user. Additionally, webhook delivery does not check if the webhook creator still has repository access before firing. This flaw allows an authenticated former admin collaborator to receive real-time data including issue titles, bodies, and commit data from private repositories, violating access controls.
Potential Impact
An authenticated former admin collaborator can continue to receive full webhook payloads from private repositories after their access has been revoked. This leads to unauthorized, ongoing, and invisible exfiltration of private repository content created after revocation. The impact crosses application boundaries by exposing data that the user should no longer access, compromising confidentiality.
Mitigation Recommendations
No official patch or fix is currently confirmed. Recommended mitigations include deleting or disabling webhooks created by a collaborator upon their access revocation, re-validating the webhook creator's repository access before each webhook delivery, or at minimum, warning administrators if a revoked user had created webhooks. Patch status is not yet confirmed — check the vendor advisory for current remediation guidance.
Gitea.dev: Gitea: Webhooks created by a collaborator keep firing after their repo access is revoked → ongoing real-time exfiltration of private repo content (CVE-2026-58440)
Description
Gitea versions prior to 1.27.0 have a vulnerability where webhooks created by a collaborator with admin permissions on a private repository continue to fire even after that collaborator's access is revoked. The webhook delivery mechanism does not re-validate the creator's current access, allowing the former collaborator to receive full payloads of repository events indefinitely. This results in ongoing, invisible exfiltration of private repository content.
CVSS v3.1
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
In Gitea (before version 1.27.0), when an admin collaborator creates a webhook on a private repository and later has their access revoked, the webhook remains active and continues to deliver event payloads to the former collaborator's endpoint. The function responsible for revoking collaboration access, DeleteCollaboration(), cleans watches and assignees but does not remove or disable webhooks created by the revoked user. Additionally, webhook delivery does not check if the webhook creator still has repository access before firing. This flaw allows an authenticated former admin collaborator to receive real-time data including issue titles, bodies, and commit data from private repositories, violating access controls.
Potential Impact
An authenticated former admin collaborator can continue to receive full webhook payloads from private repositories after their access has been revoked. This leads to unauthorized, ongoing, and invisible exfiltration of private repository content created after revocation. The impact crosses application boundaries by exposing data that the user should no longer access, compromising confidentiality.
Mitigation Recommendations
No official patch or fix is currently confirmed. Recommended mitigations include deleting or disabling webhooks created by a collaborator upon their access revocation, re-validating the webhook creator's repository access before each webhook delivery, or at minimum, warning administrators if a revoked user had created webhooks. Patch status is not yet confirmed — check the vendor advisory for current remediation guidance.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-66m4-5jjr-2rg5
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-58440"]
- Ecosystems
- ["Go"]
- Database Specific Severity
- MODERATE
- Cvss Version
- 3.1
Threat ID: 6a600abd9c2644c7f8fe2f04
Added to database: 07/22/2026, 00:11:41 UTC
Last enriched: 07/22/2026, 00:53:48 UTC
Last updated: 07/22/2026, 01:35:53 UTC
Views: 4
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.