{
  "id": "CVE-2026-100618",
  "url": "https://poc.griffinguard.io/cve/CVE-2026-100618",
  "published_at": "2026-09-26T13:22:58.212Z",
  "title": "Capgo App Icon Update Privilege Escalation via Service-Role Worker",
  "vendor": "Cap-go",
  "product": "capgo.app",
  "cvss": {
    "score": 8.7,
    "source": "cna",
    "vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N"
  },
  "kev": {
    "in_kev": false,
    "added_at": null,
    "days_after_publication": null
  },
  "first_poc": null,
  "poc_repo_count": 0,
  "exploit_count": 0,
  "suspicious_repo_count": 0,
  "edge_device": null,
  "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.",
  "cwe": "CWE-639",
  "cvss_by_source": {
    "cna": 8.7
  },
  "repos": [],
  "remediation": {
    "affected": [
      {
        "vendor": "Cap-go",
        "product": "capgo.app",
        "ranges": [
          "\u003c= *"
        ],
        "fixed_in": null
      }
    ],
    "references": [
      {
        "kind": "Vendor advisory",
        "url": "https://github.com/Cap-go/capgo.app/security/advisories/GHSA-669c-gwrr-hc53"
      }
    ]
  },
  "exploit_refs": [],
  "hunt_profile": [],
  "rules": []
}
