Is CVE-2026-56250 exploited in the wild?

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

How severe is CVE-2026-56250?

High severity, with a CVSS score of 7.5, published 8 July 2026.

Is there a fix for CVE-2026-56250?

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-56250 attacked?

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

Am I affected by CVE-2026-56250?

Check whether you run Capgo 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-56250: Capgo arbitrary R2 object deletion via mutable r2_path in app_versions

CVE-2026-56250 · Severity: high · CVSS 7.5 · Published 2026-07-08

Capgo, an over-the-air (OTA) update service for mobile applications, contained a vulnerability that allowed users with limited upload permissions to delete files belonging to other versions or users. By manipulating internal file paths, an attacker could trick the system's automated cleanup process into removing legitimate application update bundles. This results in a denial-of-service condition where users are unable to download necessary app updates, potentially disrupting business operations and application availability.

Technologies: Capgo. Vendors: Capgo.

Quick answers

Is CVE-2026-56250 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-56250 being exploited in the wild.
How severe is CVE-2026-56250?: High severity, with a CVSS score of 7.5, published 8 July 2026.
Which products and versions are affected?: Capgo < 12.128.2.
Is there a fix for CVE-2026-56250?: 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-56250 attacked?: It is attacked over the network, in a hosted service.
Am I affected by CVE-2026-56250?: Check whether you run Capgo 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

A missing authorization vulnerability (CWE-862) in Capgo's Supabase PostgREST configuration allowed upload-scoped API keys to modify the 'r2_path' field in the 'app_versions' table. While this field is intended to be server-derived, the 'Allow update for api keys' policy failed to restrict modification of this specific column. An attacker can create a version row, patch its 'r2_path' to point to a victim's R2 bundle object, and then perform a soft-delete on their own version. This triggers the 'on_version_update' cleanup function, which executes 's3.deleteObject()' on the attacker-supplied path, leading to arbitrary object deletion in the R2 bucket. The issue is fixed in version 12.128.2.

Affected products

Capgo Capgo < 12.128.2

Timeline

2026-05-07: advisory: GitHub Security Advisory published
2026-07-08: disclosed: NVD publication date

References

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