CVE-2026-100618: Authorization Bypass Through User-Controlled Key in Cap-go capgo.app
Capgo (capgo.app) is affected by an authorization flaw in the app icon update path. The PUT /app/:id endpoint accepts a user-controlled `icon` value, normalizes it, and stores it in public.apps.icon_url without verifying that the image path belongs to the target app's own image namespace (e.g. org/{owner_org}/{app_id}/...). Updating apps.icon_url fires the on_app_update trigger, whose worker reads record.icon_url and calls cleanStoredImageMetadata(), which runs with service-role credentials (supabaseAdmin()) and downloads and re-uploads the referenced storage object with upsert: true. As a result, an authenticated holder of an app-limited write API key can cause the privileged worker to rewrite an out-of-scope private image object (for example an organization logo) that the key cannot read or write directly under Supabase Storage RLS. All versions are affected; no patched version was available at the time of the advisory.
AI Analysis
Technical Summary
The vulnerability in Capgo's app icon update path arises because the PUT /app/:id endpoint accepts a user-controlled 'icon' value, normalizes it, and stores it in public.apps.icon_url without verifying that the image path belongs to the target app's namespace. When apps.icon_url is updated, an on_app_update trigger invokes a worker with service-role credentials that downloads and re-uploads the referenced storage object with upsert: true. This allows an authenticated user holding an app-limited write API key to cause the privileged worker to rewrite private image objects outside their direct read/write permissions under Supabase Storage RLS. All versions are affected, and no patch is available.
Potential Impact
An attacker with an app-limited write API key can bypass authorization controls to rewrite private image objects in Supabase Storage that they cannot directly access. This could lead to unauthorized modification of sensitive images such as organization logos. The vulnerability has a high severity with a CVSS 4.0 score of 8.7, indicating significant impact potential if exploited.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, restrict issuance of app-limited write API keys to trusted users and monitor usage for suspicious activity related to app icon updates.
CVE-2026-100618: Authorization Bypass Through User-Controlled Key in Cap-go capgo.app
Description
Capgo (capgo.app) is affected by an authorization flaw in the app icon update path. The PUT /app/:id endpoint accepts a user-controlled `icon` value, normalizes it, and stores it in public.apps.icon_url without verifying that the image path belongs to the target app's own image namespace (e.g. org/{owner_org}/{app_id}/...). Updating apps.icon_url fires the on_app_update trigger, whose worker reads record.icon_url and calls cleanStoredImageMetadata(), which runs with service-role credentials (supabaseAdmin()) and downloads and re-uploads the referenced storage object with upsert: true. As a result, an authenticated holder of an app-limited write API key can cause the privileged worker to rewrite an out-of-scope private image object (for example an organization logo) that the key cannot read or write directly under Supabase Storage RLS. All versions are affected; no patched version was available at the time of the advisory.
CVSS v4.0
Score 8.7high
Affected software
Cap-go
capgo.app
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in Capgo's app icon update path arises because the PUT /app/:id endpoint accepts a user-controlled 'icon' value, normalizes it, and stores it in public.apps.icon_url without verifying that the image path belongs to the target app's namespace. When apps.icon_url is updated, an on_app_update trigger invokes a worker with service-role credentials that downloads and re-uploads the referenced storage object with upsert: true. This allows an authenticated user holding an app-limited write API key to cause the privileged worker to rewrite private image objects outside their direct read/write permissions under Supabase Storage RLS. All versions are affected, and no patch is available.
Potential Impact
An attacker with an app-limited write API key can bypass authorization controls to rewrite private image objects in Supabase Storage that they cannot directly access. This could lead to unauthorized modification of sensitive images such as organization logos. The vulnerability has a high severity with a CVSS 4.0 score of 8.7, indicating significant impact potential if exploited.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, restrict issuance of app-limited write API keys to trusted users and monitor usage for suspicious activity related to app icon updates.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulnCheck
- Date Reserved
- 2026-09-26T02:31:07.602Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6ab7c9a1f7a7c5410652fd04
Added to database: 09/26/2026, 13:33:21 UTC
Last enriched: 09/26/2026, 14:18:40 UTC
Last updated: 09/27/2026, 04:31:33 UTC
Views: 6
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.