Is CVE-2026-56220 exploited in the wild?

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

How severe is CVE-2026-56220?

Medium severity, with a CVSS score of 6.5, published 8 July 2026.

Is there a fix for CVE-2026-56220?

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

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

Am I affected by CVE-2026-56220?

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-56220: Capgo authorization bypass in public.manifest INSERT policy

CVE-2026-56220 · Severity: medium · CVSS 6.5 · Published 2026-07-08

Capgo, an over-the-air (OTA) update service for mobile applications, contained a flaw that allowed low-privileged, read-only organization members to modify update metadata. By injecting malicious entries into the update manifest, an internal attacker could redirect user devices to download unauthorized or malicious assets. This could lead to the delivery of compromised application code to end-users, potentially impacting the security and integrity of the mobile apps relying on the service.

Technologies: Capgo. Vendors: Capgo.

Quick answers

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

An authorization bypass exists in Capgo's Supabase Row Level Security (RLS) policy for the 'public.manifest' table. The INSERT policy incorrectly validated only organization membership rather than verifying write or upload permissions. An authenticated attacker with read-only access to an organization can use Supabase PostgREST to insert rows into the manifest table with arbitrary 's3_path' values. These malicious entries are subsequently trusted by the unauthenticated '/updates' endpoint and served to mobile devices as valid OTA manifest download URLs, enabling metadata poisoning and the delivery of malicious application assets. The issue was resolved 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.