{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-100628 exists.","fix":"No fix has been published for CVE-2026-100628 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-100628 is a high-severity authentication bypass 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-100628 and fix it if it is affected.\n\nWhat it is: CVE-2026-100628 is a high-severity authentication bypass 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-100628 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-100628/ (Markdown: https://insights.sbomify.com/CVE-2026-100628/index.md)","id":"CVE-2026-100628","markdown":"https://insights.sbomify.com/CVE-2026-100628/index.md","name":"CVE-2026-100628","record":{"aliases":["GHSA-38jp-2fr7-m68g","GHSA-j6p6-qqcg-3fwp"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Capgo app","requires_auth":"low_privilege","summary":"Authenticated users can bypass API key expiration policies to create non-expiring keys, undermining security controls in Capgo.","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.app before 12.128.12 fails to enforce an organization's API key expiration policy when creating app-scoped API keys. In the POST /apikey endpoint, requests that supply app_id but omit org_id, limited_to_orgs, and expires_at resolve the target app and scope the key to it, but never add the app's owner organization to the list of organization IDs passed to validateExpirationAgainstOrgPolicies; because that list is empty, the validation returns early. As a result, an authenticated organization member can create a non-expiring app-scoped API key even when the owning organization has require_apikey_expiration enabled and a max_apikey_expiration_days limit configured. The issue is fixed in version 12.128.12.","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.app before 12.128.12 Authentication Bypass via apikey","id":"CVE-2026-100628","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 backend before 12.127.5 Privilege Escalation via role_bindings PATCH","id":"CVE-2026-100629"},"packages":[],"prev":{"headline":"Capgo bundle promotion API channel RBAC deny override bypass","id":"CVE-2026-100627"},"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":"partial"},"state":"PUBLISHED","updated":"2026-09-28","vendors":["Cap-go"]},"summary":"Authenticated users can bypass API key expiration policies to create non-expiring keys, undermining security controls in Capgo.","url":"https://insights.sbomify.com/CVE-2026-100628/"}