CVE-2026-100621

MEDIUMPre-NVD 4.34.3—
EchelonGraph scoreHIGH confidence

Score 4.3 from GitHub Security Advisory published 2026-09-26. A secondary CVSS source baseline 4.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this weekElevated
4.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 4.3Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

Capgo (capgo.app) contains an incomplete access-control/content-lock enforcement issue affecting all versions; no patch is available at the time of publication. The enforce_encrypted_bundle_trigger / check_encrypted_bundle_on_insert content lock in supabase/schemas/prod.sql exempts app_versions rows whose previous storage_provider is r2-direct, so delivery-critical columns (name, app_id, session_key, key_id, storage_provider, r2_path, external_url, checksum, manifest, native_packages) remain mutable while a row is in that state. Separately, the channel/version join used by the /updates endpoint (supabase/functions/_backend/utils/pg.ts) filters only deleted versions and does not exclude r2-direct versions, so such rows remain OTA-selectable. An attacker holding a Capgo API key with bundle write/upload permission can create or keep a bundle version in the r2-direct state, assign it to a channel, and then modify these fields via direct PostgREST requests, causing altered bundle metadata (for example checksum and session_key) to be served to devices through /updates. This bypasses the post-upload content immutability hardening added for a previous app_versions metadata-tampering issue.

CVSS v3
4.3
EG Score
4.3MEDIUMhigh confidence
EG Risk
35
EG Risk 35/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
Severity43% × 45%
Exploitation40% × 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.2%
EPSS %ILE
11th
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 public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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.app Content-Lock Bypass via r2-direct Bundle Mutation | Advisories | VulnCheck

https://www.vulncheck.com/advisories/capgo-app-content-lock-bypass-via-r2-direct-bundle-mutation
github Patch Available🟡 PoC Available

Content-lock regression allows channel-linked r2-direct bundle versions to remain OTA-selectable and mutable · Advisory · Cap-go/capgo.app · GitHub

https://github.com/Cap-go/capgo.app/security/advisories/GHSA-5rg9-rhwj-wj76

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-100621?
CVE-2026-100621 is a medium vulnerability published on September 26, 2026. Capgo (capgo.app) contains an incomplete access-control/content-lock enforcement issue affecting all versions; no patch is available at the time of publication. The enforceencryptedbundletrigger / checkencryptedbundleoninsert content lock in supabase/schemas/prod.sql exempts appversions rows whose…
When was CVE-2026-100621 disclosed?
CVE-2026-100621 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-100621 actively exploited?
CVE-2026-100621 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (11th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-100621?
CVE-2026-100621 has a CVSS base score of 4.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-100621?
A fix for CVE-2026-100621 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-100621 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-100621?

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

Book a Demo →Browse All CVEs