{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-88862 exists.","fix":"No fix has been published for CVE-2026-88862 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-88862 is a high-severity authentication bypass vulnerability in Cap-go capgo.app, published on 10 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-88862 and fix it if it is affected.\n\nWhat it is: CVE-2026-88862 is a high-severity authentication bypass vulnerability in Cap-go capgo.app, published on 10 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-88862 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-88862/ (Markdown: https://insights.sbomify.com/CVE-2026-88862/index.md)","id":"CVE-2026-88862","markdown":"https://insights.sbomify.com/CVE-2026-88862/index.md","name":"CVE-2026-88862","record":{"aliases":["GHSA-5hjr-xhx8-x5j7","GHSA-92q7-3qv3-754g"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["privilege_escalation","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Capgo API backend","requires_auth":"low_privilege","summary":"Authenticated attackers can bypass API key restrictions by supplying a privileged key ID in headers, gaining unauthorized application admin permissions.","user_interaction":"not_required","vuln_class":"auth_bypass"},"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-863","name":"Incorrect Authorization"}],"description":"Capgo (capgo.app) backend through 12.242.4 does not validate parent-child delegation when processing the x-limited-key-id header. checkKeyByIdPg() in supabase/functions/_backend/utils/hono_middleware.ts resolves the attacker-supplied numeric API key ID using only the key ID, its expiration state, and the authenticating key's user_id, while hasLimitedRbacSubkeyScope() accepts any key with a non-organization (e.g., app-scoped) RBAC binding and validateSubkeyUser() only compares owning user IDs. Because Capgo treats API keys as independent RBAC principals with separate role bindings, an authenticated apikey_manager API key with no application access can supply the numeric ID of a more privileged same-owner key and have the middleware replace the authenticated principal and effective API-key secret with that key (setSubkeyAuthContext), exercising an app_admin sibling's permissions without knowing or submitting its secret. The issue was reproduced on release 12.242.4 (commit b3d02cdbc23ac59990785acacd1f113c07458568) after the fix for GHSA-8h52-44r7-w343; at the time of the advisory no patched version was available.","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 API Key Manager Authentication Bypass via x-limited-key-id","id":"CVE-2026-88862","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"capgo.app through 12.207.1 Privilege Escalation via invite_new_user_to_org","id":"CVE-2026-88863"},"packages":[],"prev":{"headline":"Capgo AAL1 Session MFA Bypass via Direct RBAC Authorization","id":"CVE-2026-88861"},"products":["capgo.app"],"published":"2026-09-10","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":"Authenticated attackers can bypass API key restrictions by supplying a privileged key ID in headers, gaining unauthorized application admin permissions.","url":"https://insights.sbomify.com/CVE-2026-88862/"}