gitea.dev
Affected
- introduced
0, fixed1.27.0(semver)
Fixed versions
1.27.0
Fix
- Fixed version
1.27.0go get [email protected]
Advisory
Also known as: CVE-2026-58440, GO-2026-6033
Gitea: Webhooks created by a collaborator keep firing after their repo access is revoked → ongoing real-time exfiltration of private repo content
Affected product
Gitea — services/repository/collaboration.go (DeleteCollaboration) + webhook delivery
Summary
When a collaborator with admin permission on a private repo creates a webhook, that webhook keeps firing
after the collaborator's access is revoked. Gitea's revocation cleanup DeleteCollaboration removes the
collaboration record, recalculates accesses, drops watches, and unassigns issues — but it does not
remove or disable webhooks the user created, and webhook delivery never re-checks whether the creator still
has repo access. The former collaborator therefore receives the full payload (issue/comment bodies, commit
data) of all future repository events at their controlled endpoint, indefinitely and invisibly.
Affected code
services/repository/collaboration.go → DeleteCollaboration() — cleans watches/assignees only; no webhook cleanup.Steps to reproduce
Using the provided reproduction materials:
GET /api/v1/repos/admin/wh-repo (attacker) → 404.GET .../hooks → webhook still active=true.action:"opened", issue.title:"CRITICAL SECRET: …", issue.body (sentinel private key), repository.private:true.(Runtime-confirmed on gitea/gitea:1.25.4. Catcher is an internal sentinel listener; the payload is a
planted sentinel, not real data; nothing is sent to any external/metadata endpoint.)
Impact
Authenticated former admin-collaborator → ongoing real-time exfiltration of private content created after
revocation; invisible to the owner; scope crosses from the application boundary to data the user should no
longer access.
Suggested remediation
Credit
Reported as part of an incomplete-patch / authorization-residue measurement study (responsible disclosure).
Medium Basis: The source's own band: MODERATE
0, fixed 1.27.0 (semver)1.27.0
1.27.0go get [email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0