{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-100620 exists.","fix":"No fix has been published for CVE-2026-100620 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-100620 is a medium-severity vulnerability in Cap-go @capgo/cli, published on 26 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-100620 and fix it if it is affected.\n\nWhat it is: CVE-2026-100620 is a medium-severity vulnerability in Cap-go @capgo/cli, published on 26 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-100620 exists.\n\nAffected product: Cap-go @capgo/cli. 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-100620/ (Markdown: https://insights.sbomify.com/CVE-2026-100620/index.md)","id":"CVE-2026-100620","markdown":"https://insights.sbomify.com/CVE-2026-100620/index.md","name":"CVE-2026-100620","record":{"aliases":["GHSA-39p6-jffm-wc33","GHSA-wf94-285x-4cgj"],"analysis":{"component_type":"developer_tool","fix_type":"no_fix_stated","impacts":["privilege_escalation","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Capgo CLI","requires_auth":"high_privilege","summary":"Attackers with the service account key can manage all draft apps in the Google Play account due to excessive permissions granted during CLI onboarding.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":5.1,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-269","name":"Improper Privilege Management"}],"description":"Capgo CLI (npm package @capgo/cli) through 7.98.2 is affected by an over-permissioned service account in its Android onboarding flow. When onboarding via Google OAuth, the CLI invites the generated Google Play service account with the account-wide Play Console permission CAN_MANAGE_DRAFT_APPS_GLOBAL (passed as developerAccountPermissions in the Android Publisher API User create request), even though the user-facing flow states the service account is invited into a single confirmed app with release-only permissions. As a result, anyone who obtains the generated service account key (PLAY_CONFIG_JSON) can create, edit, and delete draft apps across the entire Google Play developer account rather than being limited to the selected package. No patched version 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":false,"headline":"Capgo CLI through 7.98.2 Excessive Permissions via Overpermissioned Play Console Service Account","id":"CVE-2026-100620","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"capgo.app Content-Lock Bypass via r2-direct Bundle Mutation","id":"CVE-2026-100621"},"packages":[],"prev":{"headline":"Capgo OTA Manifest Poisoning via app_versions.manifest Bypass","id":"CVE-2026-100619"},"products":["@capgo/cli"],"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":"partial"},"state":"PUBLISHED","updated":"2026-10-05","vendors":["Cap-go"]},"summary":"Attackers with the service account key can manage all draft apps in the Google Play account due to excessive permissions granted during CLI onboarding.","url":"https://insights.sbomify.com/CVE-2026-100620/"}