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.

CVE-2026-81035 affects Midday, a financial management platform, where any team member regardless of role can delete an entire team. The vulnerability exists in apps/api/src/trpc/routers/team.ts, where the delete procedure uses only the team-access helper for authorization, which returns true for all team members without checking their role. Other procedures in the same router correctly enforce owner-only access for sensitive operations, but this check was never applied to the delete endpoint. Any invited user with the default 'Member' role can exploit this to permanently delete a team and all associated records. The deletion also triggers a cleanup job that uses stored bank-connection tokens against connected financial providers, potentially causing broader damage. Additionally, the update procedure in the same router also lacks any role check, widening the attack surface. The impact includes unauthorized data destruction and potential abuse of stored financial credentials.