Is CVE-2026-100627 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-100627 being exploited in the wild.

How severe is CVE-2026-100627?

High severity, with a CVSS score of 8.1, published 26 September 2026.

Which products and versions are affected?

Cap-go Capgo server backend main at de66fa51e7ff2f50283cc1455c3d80ab3eb0ae43 and likely earlier versions.

Is there a fix for CVE-2026-100627?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2026-100627 attacked?

It is attacked over the network, in a hosted service.

Am I affected by CVE-2026-100627?

Check whether you run Cap-go Capgo server backend at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-100627: Capgo server backend bundle promotion API authorization bypass

CVE-2026-100627 · Severity: high · CVSS 8.1 · Published 2026-09-26

Capgo is an over-the-air update platform for mobile apps. A flaw in the bundle promotion API allows developers or uploaders who have been explicitly blocked from promoting bundles to specific production channels to bypass that restriction and force deployments anyway. This could enable restricted team members to push malicious or untested app updates to end-user devices despite administrative controls intended to prevent it.

Vendors: Cap-go.

Quick answers

Is CVE-2026-100627 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-100627 being exploited in the wild.
How severe is CVE-2026-100627?: High severity, with a CVSS score of 8.1, published 26 September 2026.
Which products and versions are affected?: Cap-go Capgo server backend main at de66fa51e7ff2f50283cc1455c3d80ab3eb0ae43 and likely earlier versions.
Is there a fix for CVE-2026-100627?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-100627 attacked?: It is attacked over the network, in a hosted service.
Am I affected by CVE-2026-100627?: Check whether you run Cap-go Capgo server backend at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The PUT /bundle endpoint accepts write/all API keys and dispatches to setChannel for authorization, which checks channel.promote_bundle permission at app scope only by omitting the channel_id parameter. Since the omitted scope field is passed to rbac_check_permission_direct as SQL NULL, the per-channel RBAC override evaluation gate (p_channel_id IS NOT NULL) is never satisfied, allowing principals with app-level channel.promote_bundle to bypass per-channel deny overrides and update channels.version for any channel. The vulnerability is confirmed in the main branch at commit de66fa51e7ff2f50283cc1455c3d80ab3eb0ae43 with no known patched version at publication.

Affected products

Cap-go Capgo server backend main at de66fa51e7ff2f50283cc1455c3d80ab3eb0ae43 and likely earlier versions

Timeline

2026-09-26: disclosed
2026-09-09: advisory: GitHub Security Advisory GHSA-633x-9x77-77gf published

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.