{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-100619 exists.","fix":"No fix has been published for CVE-2026-100619 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-100619 is a high-severity missing authorization vulnerability in Cap-go capgo.app, published on 26 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-100619 and fix it if it is affected.\n\nWhat it is: CVE-2026-100619 is a high-severity missing authorization vulnerability in Cap-go capgo.app, published on 26 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-100619 exists.\n\nAffected product: Cap-go capgo.app. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-100619/ (Markdown: https://insights.sbomify.com/CVE-2026-100619/index.md)","id":"CVE-2026-100619","markdown":"https://insights.sbomify.com/CVE-2026-100619/index.md","name":"CVE-2026-100619","record":{"aliases":["GHSA-xj78-q428-xww2"],"analysis":{"component_type":"cloud_service","fix_type":"no_fix_stated","impacts":["code_execution","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Capgo OTA service","requires_auth":"low_privilege","summary":"Attackers with write access can poison OTA manifests via a trusted async worker, enabling malicious code execution on client devices.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-266","name":"Incorrect Privilege Assignment"}],"description":"Capgo (capgo.app) blocks direct user inserts into the public.manifest table with a RESTRICTIVE row-level security policy, but that restriction can be bypassed indirectly. A principal holding an app-scoped upload/write/all API key (upload+ rights) or an authenticated user with write+ rights on an app can update public.app_versions.manifest on a version whose storage_provider is 'r2-direct', which is not covered by the bundle content-lock check. The on_version_update async worker trusts record.manifest and, using the service-role Supabase client, inserts the attacker-controlled file_name, file_hash, and s3_path into public.manifest before clearing app_versions.manifest. When a channel points to the crafted version, the /updates endpoint returns the service-role-created manifest entry as a client-facing download_url, enabling OTA manifest poisoning through a trusted async worker path. All versions are affected; no patch was available at the time of publication.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Capgo OTA Manifest Poisoning via app_versions.manifest Bypass","id":"CVE-2026-100619","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Capgo CLI through 7.98.2 Excessive Permissions via Overpermissioned Play Console Service Account","id":"CVE-2026-100620"},"packages":[],"prev":{"headline":"Capgo App Icon Update Privilege Escalation via Service-Role Worker","id":"CVE-2026-100618"},"products":["capgo.app"],"published":"2026-09-26","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-09-30","vendors":["Cap-go"]},"summary":"Attackers with write access can poison OTA manifests via a trusted async worker, enabling malicious code execution on client devices.","url":"https://insights.sbomify.com/CVE-2026-100619/"}