{
  "id": "CVE-2026-100628",
  "url": "https://poc.griffinguard.io/cve/CVE-2026-100628",
  "published_at": "2026-09-26T13:23:05.038Z",
  "title": "capgo.app before 12.128.12 Authentication Bypass via apikey",
  "vendor": "Cap-go",
  "product": "capgo.app",
  "cvss": {
    "score": 8.7,
    "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"
  },
  "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.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.",
  "cwe": "CWE-863",
  "cvss_by_source": {
    "cna": 8.7
  },
  "repos": [],
  "remediation": {
    "affected": [
      {
        "vendor": "Cap-go",
        "product": "capgo.app",
        "ranges": [
          "\u003c 12.128.12"
        ],
        "fixed_in": [
          "12.128.12"
        ]
      }
    ],
    "upgrade": [
      "Upgrade capgo.app to 12.128.12 or later."
    ],
    "references": [
      {
        "kind": "Vendor advisory",
        "url": "https://github.com/Cap-go/capgo.app/security/advisories/GHSA-j6p6-qqcg-3fwp"
      }
    ]
  },
  "exploit_refs": [],
  "hunt_profile": [],
  "rules": []
}
