CVE-2026-100612

HIGHPre-NVD 7.27.2—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.2EG
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: 7.2Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Capgo (capgo.app) through version 12.261.0 contains an incomplete access-control fix for the public.sso_providers table. Migration 20260826100000_sso_providers_block_direct_active_insert.sql installs a BEFORE UPDATE guard (enforce_sso_provider_client_update_guard()) that freezes only the dns_verified_at, domain, status and enforce_sso columns; provider_id (as well as metadata_url and attribute_mapping) is left writable. Because the table is granted ALL to the anon and authenticated roles with no column-level restriction, and PostgreSQL row-level security policies such as allow_org_admins_update_sso_providers constrain only which row may be updated and not which columns, a user holding the org_admin tier permission org.update_settings can PATCH provider_id over PostgREST to an identity provider under their control. Since provider_id is the trust anchor binding an email domain to an authorized IdP, the attacker can then authenticate through their own IdP while asserting the org owner's email; the server-side provider match succeeds and the merge routine attaches the attacker's SSO identity to the existing owner account, nulls its password, and deletes its other identities and sessions. This results in vertical privilege escalation from org_admin to org owner/super_admin, account takeover, and lockout of the legitimate owner. Exploitation requires that the target organization has an active SSO provider configured and that the attacker already holds org_admin in that organization. No patched version is available.

CVSS v3
7.2
EG Score
7.2HIGHhigh confidence
EG Risk
33
EG Risk 33/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
Severity72% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
24th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (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 SSO Provider ID Authentication Bypass via Incomplete Migration | Advisories | VulnCheck

https://www.vulncheck.com/advisories/capgo-sso-provider-id-authentication-bypass-via-incomplete-migration
github Patch Available🟡 PoC Available

SSO provider_id is client-writable — incomplete fix in the latest migration lets an org admin hijack the org owner account · Advisory · Cap-go/capgo.app · GitHub

https://github.com/Cap-go/capgo.app/security/advisories/GHSA-jpjp-v827-j4gc

Vendor Advisories for CVE-2026-100612(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 33× 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 04:22 UTCGHSA enrichment
  2. 2026-10-03 17:07 UTCEG score recompute
  3. 2026-10-03 17:06 UTCGHSA enrichment
  4. 2026-10-03 14:25 UTCEPSS rescore
  5. 2026-10-03 05:50 UTCGHSA enrichment
  6. 2026-10-02 18:34 UTCEG score recompute
  7. 2026-10-02 18:34 UTCGHSA enrichment
  8. 2026-10-02 07:18 UTCGHSA enrichment
  9. 2026-10-01 20:02 UTCEG score recompute
  10. 2026-10-01 20:02 UTCGHSA enrichment
  11. 2026-10-01 19:49 UTCEPSS rescore
  12. 2026-10-01 08:46 UTCGHSA enrichment
  13. 2026-09-30 21:30 UTCEG score recompute
  14. 2026-09-30 21:30 UTCGHSA enrichment
  15. 2026-09-30 20:27 UTCEG score recompute
  16. 2026-09-30 20:27 UTCGHSA enrichment
  17. 2026-09-30 18:41 UTCEG score recompute
  18. 2026-09-30 18:41 UTCGHSA enrichment
  19. 2026-09-30 17:38 UTCEG score recompute
  20. 2026-09-30 17:38 UTCGHSA enrichment
  21. 2026-09-30 15:02 UTCEPSS rescore
  22. 2026-09-30 06:48 UTCGHSA enrichment
  23. 2026-09-29 19:32 UTCEG score recompute
  24. 2026-09-29 19:32 UTCGHSA enrichment
  25. 2026-09-29 15:20 UTCEPSS rescore
Show 14 more
  1. 2026-09-29 08:14 UTCEG score recompute
  2. 2026-09-29 08:14 UTCGHSA enrichment
  3. 2026-09-28 20:58 UTCEG score recompute
  4. 2026-09-28 20:58 UTCGHSA enrichment
  5. 2026-09-28 13:50 UTCEPSS rescore
  6. 2026-09-28 11:43 UTCGHSA enrichment
  7. 2026-09-28 00:26 UTCEG score recompute
  8. 2026-09-28 00:26 UTCGHSA enrichment
  9. 2026-09-27 13:10 UTCGHSA enrichment
  10. 2026-09-27 01:54 UTCEG score recompute
  11. 2026-09-27 01:54 UTCGHSA enrichment
  12. 2026-09-26 14:35 UTCEG score recompute
  13. 2026-09-26 13:41 UTCEG score recompute
  14. 2026-09-26 13:30 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-100612?
CVE-2026-100612 is a high vulnerability published on September 26, 2026. Capgo (capgo.app) through version 12.261.0 contains an incomplete access-control fix for the public.ssoproviders table. Migration 20260826100000ssoprovidersblockdirectactiveinsert.sql installs a BEFORE UPDATE guard (enforcessoproviderclientupdateguard()) that freezes only the dnsverifiedat, domain,…
When was CVE-2026-100612 disclosed?
CVE-2026-100612 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-100612 actively exploited?
CVE-2026-100612 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (24th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-100612?
CVE-2026-100612 has a CVSS base score of 7.2 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-100612?
A fix for CVE-2026-100612 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-100612 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-100612?

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