CVE-2026-81035

HIGHPre-NVD 8.18.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-08-26. A secondary CVSS source baseline 8.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this weekElevated
8.1EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 8.1Exploit: No code on recordExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

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.

CVSS v3
8.1
EG Score
8.1HIGHmedium confidence
EG Risk
52
EG Risk 52/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity81% × 45%
The EG Score, 8.1 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.3%
EPSS %ILE
25th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 26, 2026

Last Modified

September 24, 2026

Advisory Details (4)

Auto-updated Aug 26, 2026
No fix on record yet.
Web page

Midday Missing Owner Check on Team Deletion | Advisories | VulnCheck

https://www.vulncheck.com/advisories/midday-missing-owner-check-on-team-deletion
Web page

midday/apps/api/src/trpc/routers/team.ts at e5f45ed0d49cdb34576373623c4579b72daa74c1 · midday-ai/midday · GitHub

https://github.com/midday-ai/midday/blob/e5f45ed0d49cdb34576373623c4579b72daa74c1/apps/api/src/trpc/routers/team.ts
Web page

[Security] Any team member can delete the entire team - midday tRPC team.delete missing owner check · Issue #890 · midday-ai/midday · GitHub

https://github.com/midday-ai/midday/issues/890
Web page

GitHub - midday-ai/midday: Invoicing, Time tracking, File reconciliation, Storage, Financial Overview & your own Assistant made for Freelancers · GitHub

https://github.com/midday-ai/midday

Vendor Advisories for CVE-2026-81035(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 19× in last 7d / 106× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 181 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 81 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  2. 2026-10-13 06:23 UTCEG score recompute
  3. 2026-10-13 06:23 UTCGHSA enrichmentGHSA-432v-m2wc-4w5v · GitHub severity HIGH · GitHub CVSS 8.1
  4. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  5. 2026-10-12 14:57 UTCEG score recompute
  6. 2026-10-11 19:21 UTCEG score recompute
  7. 2026-10-11 16:37 UTCEG score recompute
  8. 2026-10-11 13:55 UTCEG score recompute
  9. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  10. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  11. 2026-10-10 06:06 UTCEG score recompute
  12. 2026-10-10 06:06 UTCGHSA enrichmentGHSA-432v-m2wc-4w5v · GitHub severity HIGH · GitHub CVSS 8.1
  13. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  14. 2026-10-09 03:22 UTCEG score recompute
  15. 2026-10-09 03:22 UTCGHSA enrichmentGHSA-432v-m2wc-4w5v · GitHub severity HIGH · GitHub CVSS 8.1
  16. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  17. 2026-10-08 01:49 UTCEG score recompute
  18. 2026-10-08 01:48 UTCGHSA enrichmentGHSA-432v-m2wc-4w5v · GitHub severity HIGH · GitHub CVSS 8.1
  19. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  20. 2026-10-07 06:36 UTCGHSA enrichmentGHSA-432v-m2wc-4w5v · GitHub severity HIGH · GitHub CVSS 8.1
  21. 2026-10-06 19:16 UTCEG score recompute
  22. 2026-10-06 19:16 UTCGHSA enrichmentGHSA-432v-m2wc-4w5v · GitHub severity HIGH · GitHub CVSS 8.1
  23. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  24. 2026-10-06 07:35 UTCEG score recompute
  25. 2026-10-06 07:35 UTCGHSA enrichmentGHSA-432v-m2wc-4w5v · GitHub severity HIGH · GitHub CVSS 8.1
Show 75 more
  1. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  2. 2026-10-05 16:54 UTCGHSA enrichmentGHSA-432v-m2wc-4w5v · GitHub severity HIGH · GitHub CVSS 8.1
  3. 2026-10-05 03:44 UTCEG score recompute
  4. 2026-10-05 03:44 UTCGHSA enrichmentGHSA-432v-m2wc-4w5v · GitHub severity HIGH · GitHub CVSS 8.1
  5. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  6. 2026-10-04 16:03 UTCGHSA enrichmentGHSA-432v-m2wc-4w5v · GitHub severity HIGH · GitHub CVSS 8.1
  7. 2026-10-04 04:44 UTCGHSA enrichmentGHSA-432v-m2wc-4w5v · GitHub severity HIGH · GitHub CVSS 8.1
  8. 2026-10-03 17:23 UTCEG score recompute
  9. 2026-10-03 17:23 UTCGHSA enrichmentGHSA-432v-m2wc-4w5v · GitHub severity HIGH · GitHub CVSS 8.1
  10. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  11. 2026-10-03 06:04 UTCGHSA enrichmentGHSA-432v-m2wc-4w5v · GitHub severity HIGH · GitHub CVSS 8.1
  12. 2026-10-02 18:34 UTCEG score recompute
  13. 2026-10-02 18:34 UTCGHSA enrichmentGHSA-432v-m2wc-4w5v · GitHub severity HIGH · GitHub CVSS 8.1
  14. 2026-10-02 17:57 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  15. 2026-10-02 07:14 UTCGHSA enrichmentGHSA-432v-m2wc-4w5v · GitHub severity HIGH · GitHub CVSS 8.1
  16. 2026-10-01 19:55 UTCEG score recompute
  17. 2026-10-01 19:55 UTCGHSA enrichmentGHSA-432v-m2wc-4w5v · GitHub severity HIGH · GitHub CVSS 8.1
  18. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  19. 2026-10-01 07:16 UTCGHSA enrichmentGHSA-432v-m2wc-4w5v · GitHub severity HIGH · GitHub CVSS 8.1
  20. 2026-09-30 19:58 UTCEG score recompute
  21. 2026-09-30 19:58 UTCGHSA enrichmentGHSA-432v-m2wc-4w5v · GitHub severity HIGH · GitHub CVSS 8.1
  22. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  23. 2026-09-30 06:02 UTCEG score recompute
  24. 2026-09-30 06:02 UTCGHSA enrichmentGHSA-432v-m2wc-4w5v · GitHub severity HIGH · GitHub CVSS 8.1
  25. 2026-09-29 08:40 UTCEG score recompute
  26. 2026-09-29 08:40 UTCGHSA enrichmentGHSA-432v-m2wc-4w5v · GitHub severity HIGH · GitHub CVSS 8.1
  27. 2026-09-28 21:20 UTCEG score recompute
  28. 2026-09-28 21:20 UTCGHSA enrichmentGHSA-432v-m2wc-4w5v · GitHub severity HIGH · GitHub CVSS 8.1
  29. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  30. 2026-09-28 06:31 UTCGHSA enrichmentGHSA-432v-m2wc-4w5v · GitHub severity HIGH · GitHub CVSS 8.1
  31. 2026-09-27 19:13 UTCEG score recompute
  32. 2026-09-27 19:13 UTCGHSA enrichmentGHSA-432v-m2wc-4w5v · GitHub severity HIGH · GitHub CVSS 8.1
  33. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  34. 2026-09-27 07:54 UTCGHSA enrichmentGHSA-432v-m2wc-4w5v · GitHub severity HIGH · GitHub CVSS 8.1
  35. 2026-09-26 20:35 UTCEG score recompute
  36. 2026-09-26 20:34 UTCGHSA enrichmentGHSA-432v-m2wc-4w5v · GitHub severity HIGH · GitHub CVSS 8.1
  37. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  38. 2026-09-25 08:33 UTCGHSA enrichmentGHSA-432v-m2wc-4w5v · GitHub severity HIGH · GitHub CVSS 8.1
  39. 2026-09-24 21:14 UTCEG score recompute
  40. 2026-09-24 21:14 UTCGHSA enrichmentGHSA-432v-m2wc-4w5v · GitHub severity HIGH · GitHub CVSS 8.1
  41. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  42. 2026-09-24 11:28 UTCGHSA enrichmentGHSA-432v-m2wc-4w5v · GitHub severity HIGH · GitHub CVSS 8.1
  43. 2026-09-24 00:10 UTCEG score recompute
  44. 2026-09-24 00:10 UTCGHSA enrichmentGHSA-432v-m2wc-4w5v · GitHub severity HIGH · GitHub CVSS 8.1
  45. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  46. 2026-09-23 12:50 UTCGHSA enrichmentGHSA-432v-m2wc-4w5v · GitHub severity HIGH · GitHub CVSS 8.1
  47. 2026-09-23 01:31 UTCEG score recompute
  48. 2026-09-23 01:31 UTCGHSA enrichmentGHSA-432v-m2wc-4w5v · GitHub severity HIGH · GitHub CVSS 8.1
  49. 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  50. 2026-09-22 14:12 UTCGHSA enrichmentGHSA-432v-m2wc-4w5v · GitHub severity HIGH · GitHub CVSS 8.1
  51. 2026-09-22 02:52 UTCEG score recompute
  52. 2026-09-22 02:52 UTCGHSA enrichmentGHSA-432v-m2wc-4w5v · GitHub severity HIGH · GitHub CVSS 8.1
  53. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  54. 2026-09-21 15:31 UTCGHSA enrichmentGHSA-432v-m2wc-4w5v · GitHub severity HIGH · GitHub CVSS 8.1
  55. 2026-09-21 04:11 UTCEG score recompute
  56. 2026-09-21 04:11 UTCGHSA enrichmentGHSA-432v-m2wc-4w5v · GitHub severity HIGH · GitHub CVSS 8.1
  57. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  58. 2026-09-20 16:52 UTCGHSA enrichmentGHSA-432v-m2wc-4w5v · GitHub severity HIGH · GitHub CVSS 8.1
  59. 2026-09-20 05:33 UTCGHSA enrichmentGHSA-432v-m2wc-4w5v · GitHub severity HIGH · GitHub CVSS 8.1
  60. 2026-09-19 18:14 UTCEG score recompute
  61. 2026-09-19 18:14 UTCGHSA enrichmentGHSA-432v-m2wc-4w5v · GitHub severity HIGH · GitHub CVSS 8.1
  62. 2026-09-19 06:54 UTCGHSA enrichmentGHSA-432v-m2wc-4w5v · GitHub severity HIGH · GitHub CVSS 8.1
  63. 2026-09-18 19:35 UTCEG score recompute
  64. 2026-09-18 19:35 UTCGHSA enrichmentGHSA-432v-m2wc-4w5v · GitHub severity HIGH · GitHub CVSS 8.1
  65. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  66. 2026-09-18 08:16 UTCGHSA enrichmentGHSA-432v-m2wc-4w5v · GitHub severity HIGH · GitHub CVSS 8.1
  67. 2026-09-17 20:57 UTCEG score recompute
  68. 2026-09-17 20:57 UTCGHSA enrichmentGHSA-432v-m2wc-4w5v · GitHub severity HIGH · GitHub CVSS 8.1
  69. 2026-09-17 06:52 UTCGHSA enrichmentGHSA-432v-m2wc-4w5v · GitHub severity HIGH · GitHub CVSS 8.1
  70. 2026-09-16 19:06 UTCEG score recompute
  71. 2026-09-16 19:06 UTCGHSA enrichmentGHSA-432v-m2wc-4w5v · GitHub severity HIGH · GitHub CVSS 8.1
  72. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  73. 2026-09-16 05:49 UTCEG score recompute
  74. 2026-09-16 05:49 UTCGHSA enrichmentGHSA-432v-m2wc-4w5v · GitHub severity HIGH · GitHub CVSS 8.1
  75. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.3% · 20th percentile

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-81035?
CVE-2026-81035 is a high-severity vulnerability; its CVE record was published on August 26, 2026. 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…
When was CVE-2026-81035 made public?
CVE-2026-81035 was made public on August 26, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on August 26, 2026. EchelonGraph's copy of the record carries a last-modified date of September 24, 2026; the record at its source may have been updated since.
Is CVE-2026-81035 actively exploited?
CVE-2026-81035 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (25th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-81035?
CVE-2026-81035 has a CVSS base score of 8.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-81035?
No fix for CVE-2026-81035 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-81035 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-81035

Explore →

Is Your Infrastructure Affected by CVE-2026-81035?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs