Quick answers
- Is CVE-2026-100618 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-100618 being exploited in the wild.
- How severe is CVE-2026-100618?
- High severity, with a CVSS score of 8.5, published 26 September 2026.
- Which products and versions are affected?
- Capgo.App all.
- Is there a fix for CVE-2026-100618?
- 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-100618 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-100618?
- Check whether you run Capgo.App 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 /app/:id endpoint accepts an arbitrary icon path, normalizes it, and stores it in apps.icon_url without validating the path belongs to the target app's namespace. The update triggers on_app_update, a background worker running with supabaseAdmin() credentials that calls cleanStoredImageMetadata() and re-uploads the referenced storage object with upsert: true. An app-limited write API key can thus indirectly modify out-of-scope private objects (e.g., org/{owner_org}/logo) that Supabase Storage RLS would normally deny. All versions are vulnerable; no fix existed at the time of publication.
Affected products
- Capgo capgo.app all
Timeline
- 2026-09-26: disclosed: Public disclosure via GitHub Security Advisory and NVD