VulnerabilityPublished 26 Sep 2026Updated 5 Oct 2026

CVE-2026-100616: Cap-go capgo.app · Incorrect Authorization

Affects Cap-go capgo.appSource CVE Database V5

Compare

Not known to be exploited · CVSS 7.0 High.

Data as of 9 Nov 2026, 23:24 UTC

CVSS 4.0 base score

7.0High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 25% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: High
User Interaction: None
Vulnerable system confidentiality: None
Vulnerable system integrity: Low
Vulnerable system availability: High
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: High: The attacker requires privileges that provide significant (e.g., administrative) control over the vulnerable system allowing full access to the vulnerable system’s settings and files.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: High: There is a total loss of availability, resulting in the attacker being able to fully deny access to resources in the Vulnerable System; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the Vulnerable System (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 26 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 10 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Cap-gocapgo.app	Affected All versions	Fixed in–

AI-suggested

Organizations should monitor for unauthorized direct updates to the public.orgs table via Supabase PostgREST and restrict access to org.update_settings permissions carefully. Avoid allowing organization admins to perform direct database updates outside the official update endpoint until a fix is released. Check the vendor advisory regularly for updates on remediation.

Description

CVE-2026-100616 is an authorization vulnerability in capgo.app, an over-the-air update platform for Capacitor apps. The flaw allows an organization admin with the org.update_settings permission to update the entire row in the public.orgs table, including the internal billing pointer customer_id, by bypassing the official update endpoint restrictions. This can corrupt or nullify the Stripe customer pointer, causing billing and plan checks to fail and resulting in the organization being treated as unpaid or without a plan. No patched version is currently available.

Impact

An authenticated organization admin without billing update permissions can corrupt or nullify the Stripe customer_id pointer, causing billing and plan validation failures. This results in the organization losing its paid plan status and being treated as unpaid or having no plan, potentially disrupting service or billing processes. The vulnerability does not allow privilege escalation beyond the organization admin role but impacts billing integrity and service continuity.

Summary

The vulnerability arises from an incorrect authorization policy on the public.orgs table's row-level security UPDATE policy in capgo.app. Although the official organization update endpoint restricts editable fields and excludes the customer_id, the row-level security policy permits an authenticated organization admin (with org.update_settings) to update the entire row directly via Supabase PostgREST. This bypass allows modification of the customer_id field without requiring the org.update_billing permission, which is normally required for billing-related updates. Exploiting this flaw can corrupt the Stripe billing pointer, causing the system to treat the organization as unpaid or without a valid plan.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 10 Oct 2026, 21:10 UTC

Technical details

References

Community reviews

Related threats