CVE-2026-100623

HIGHPre-NVD 8.88.8—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this weekElevated
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 8.8Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

Capgo (capgo.app) exposes the legacy membership table public.org_users directly through Supabase PostgREST. The table's row-level security policies "Allow org admin to insert" and "Allow org admin to update" only verify that the caller has admin rights in the target organization (public.check_min_rights('admin', ...)); they do not require a pending invitation in tmp_users, acceptance of an invite token via /private/accept_invitation, any action by the target user, or the membership/role-consistency and anti-escalation checks enforced by the RBAC role-binding path. As a result, an authenticated user who is an admin of an organization can INSERT or UPDATE org_users rows directly to add any existing public.users account as an active member of that organization with user_right="admin", bypassing the invitation and role-assignment workflow entirely. In testing, an account with no prior access to the organization or its apps could, after such a direct insert, read the organization and app and pass check_min_rights. All versions are affected and no patch was available at the time of publication.

CVSS v3
8.8
EG Score
8.8HIGHhigh confidence
EG Risk
56
EG Risk 56/100CISA SSVC

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
Severity88% × 45%
Exploitation40% × 40%
Automatability0% × 15%
CISA SSVC: Track at low, Track* at medium and Attend at high mission impact.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.3%
EPSS %ILE
22nd
KEV
Not listed

CISA SSVCTrack at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 26, 2026

Last Modified

September 30, 2026

Advisory Details (2)

Auto-updated Sep 26, 2026
🔬 Proof of concept available. Patch available. Sources: github.
generic

Capgo Authentication Bypass via Direct PostgREST org_users Table Write | Advisories | VulnCheck

https://www.vulncheck.com/advisories/capgo-authentication-bypass-via-direct-postgrest-org-users-table-write
github Patch Available🟡 PoC Available

Direct PostgREST writes to public.org_users bypass invite acceptance and add arbitrary existing users as active org admins · Advisory · Cap-go/capgo.app · GitHub

https://github.com/Cap-go/capgo.app/security/advisories/GHSA-w349-9mc3-8c5x

Vendor Advisories for CVE-2026-100623(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 34× in last 7d / 39× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-10-04 08:03 UTCGHSA enrichment
  2. 2026-10-03 19:48 UTCEG score recompute
  3. 2026-10-03 19:48 UTCGHSA enrichment
  4. 2026-10-03 14:25 UTCEPSS rescore
  5. 2026-10-03 07:37 UTCGHSA enrichment
  6. 2026-10-02 19:25 UTCEG score recompute
  7. 2026-10-02 19:25 UTCGHSA enrichment
  8. 2026-10-02 07:14 UTCEG score recompute
  9. 2026-10-02 07:14 UTCGHSA enrichment
  10. 2026-10-01 19:49 UTCEPSS rescore
  11. 2026-10-01 19:03 UTCGHSA enrichment
  12. 2026-10-01 06:52 UTCGHSA enrichment
  13. 2026-09-30 18:41 UTCEG score recompute
  14. 2026-09-30 18:41 UTCGHSA enrichment
  15. 2026-09-30 17:37 UTCEG score recompute
  16. 2026-09-30 17:37 UTCGHSA enrichment
  17. 2026-09-30 15:02 UTCEPSS rescore
  18. 2026-09-30 11:59 UTCGHSA enrichment
  19. 2026-09-29 23:48 UTCEG score recompute
  20. 2026-09-29 23:48 UTCGHSA enrichment
  21. 2026-09-29 15:20 UTCEPSS rescore
  22. 2026-09-29 09:23 UTCEG score recompute
  23. 2026-09-29 09:23 UTCGHSA enrichment
  24. 2026-09-28 21:13 UTCGHSA enrichment
  25. 2026-09-28 17:43 UTCEG score recompute
Show 14 more
  1. 2026-09-28 17:42 UTCGHSA enrichment
  2. 2026-09-28 17:14 UTCEG score recompute
  3. 2026-09-28 17:13 UTCGHSA enrichment
  4. 2026-09-28 15:21 UTCEG score recompute
  5. 2026-09-28 15:21 UTCGHSA enrichment
  6. 2026-09-28 13:50 UTCEPSS rescore
  7. 2026-09-28 03:10 UTCGHSA enrichment
  8. 2026-09-27 14:59 UTCEG score recompute
  9. 2026-09-27 14:58 UTCGHSA enrichment
  10. 2026-09-27 02:46 UTCEG score recompute
  11. 2026-09-27 02:46 UTCGHSA enrichment
  12. 2026-09-26 14:35 UTCEG score recompute
  13. 2026-09-26 13:40 UTCEG score recompute
  14. 2026-09-26 13:30 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-100623?
CVE-2026-100623 is a high vulnerability published on September 26, 2026. Capgo (capgo.app) exposes the legacy membership table public.orgusers directly through Supabase PostgREST. The table's row-level security policies "Allow org admin to insert" and "Allow org admin to update" only verify that the caller has admin rights in the target organization…
When was CVE-2026-100623 disclosed?
CVE-2026-100623 was first published on September 26, 2026, with the most recent update on September 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-100623 actively exploited?
CVE-2026-100623 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (22nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-100623?
CVE-2026-100623 has a CVSS base score of 8.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-100623?
A fix for CVE-2026-100623 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-100623 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-100623?

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