CVE-2026-81035: Midday Missing Owner Check on Team Deletion
Midday allows any member of a team to delete it. The delete procedure in apps/api/src/trpc/routers/team.ts authorises the caller with the team-access helper, which returns true for every row in the team-membership table irrespective of the role it records, and the data-layer function it calls re-checks the same helper and nothing else. The neighbouring procedures that remove or update a member in the same router each resolve the caller's role and refuse the request unless it is owner, so the check exists in the file and is not applied to deletion. Member is the role an invited user receives, so any invitee can remove the team and every record scoped to it, and the deletion enqueues the cleanup job with the stored bank-connection tokens, which the job then uses against the connected providers. The update procedure in the same router carries no role check either.
Affected Software
Event History
Frequently Asked Questions
Which users can exploit this issue?
Any user recorded in the team-membership table can delete the team, including an invited user with the default Member role. The caller must be authenticated as a member of the target team; no owner role is required.
What is the impact of a successful deletion?
The team and every record scoped to it can be removed. Deletion also queues a cleanup job that uses the team's stored bank-connection tokens against connected providers.
Are related team-management actions also missing an owner check?
The team update procedure in the same router also has no role check. In contrast, the procedures for removing or updating a member explicitly resolve the caller's role and require owner privileges.