---
id: CVE-2026-81035
title: Midday allows any member of a team to delete it
summary: >-
  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 t…
severity: high
cvss: 8.1
cvssVector: 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H'
cwe:
  - CWE-862
published: '2026-08-26'
updated: '2026-09-24'
sourceUpdated: '2026-09-24T20:43:32.537'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-81035'
references:
  - url: 'https://github.com/midday-ai/midday'
    label: disclosure@vulncheck.com
  - url: >-
      https://github.com/midday-ai/midday/blob/e5f45ed0d49cdb34576373623c4579b72daa74c1/apps/api/src/trpc/routers/team.ts
    label: disclosure@vulncheck.com
  - url: 'https://github.com/midday-ai/midday/issues/890'
    label: disclosure@vulncheck.com
  - url: >-
      https://www.vulncheck.com/advisories/midday-missing-owner-check-on-team-deletion
    label: disclosure@vulncheck.com
  - url: 'https://github.com/midday-ai/midday/issues/890'
    label: 134c704f-9b21-4f2e-91b3-4a467353bcc0
tags:
  - nvd
epss: 0.00504
epssPercentile: 0.40465
ingestedAt: '2026-09-24T20:51:40.233Z'
---

## Overview

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.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
