CVE-2026-100611
NVD: Capgo (capgo.app backend, versions ≤ 12.261.0) improperly restricts which roles the apikey_manager organization role may bind to newly created API keys. NVD: When an authenticated user holding only apikey_manager (permissions org.manage_apikeys and org.read) calls POST /apikey with a JWT session, the only checks applied are the org.manage_apikeys permission, a fixed deny-list of assignable role names... NVD: No check verifies that the caller actually holds the permissions conferred by the role being assigned.
7.1 Severity
HIGH EPSS
0.0022 (11) KEV
-
Source-published summary
NVD: Capgo (capgo.app backend, versions ≤ 12.261.0) improperly restricts which roles the apikey_manager organization role may bind to newly created API keys. NVD: When an authenticated user holding only apikey_manager (permissions org.manage_apikeys and org.read) calls POST /apikey with a JWT session, the only checks applied are the org.manage_apikeys permission, a fixed deny-list of assignable role names... NVD: No check verifies that the caller actually holds the permissions conferred by the role being assigned.
Possible impact
Source describes privilege escalation risk · authenticated boundary. Possible impact: An attacker may cross a privilege boundary and gain more access than intended.
Affected context
Affected product or version requires source confirmation.
Remediation / advisory
Remediation reference present; patch status requires confirmation in the linked advisory.
Why it matters
Source describes privilege escalation risk · authenticated boundary. Possible impact: An attacker may cross a privilege boundary and gain more access than intended.; CVSS 7.1 (HIGH); EPSS percentile 11; not listed in KEV; Remediation reference present; patch status requires confirmation in the linked advisory; sources: NVD, OSV.
What to verify
Confirm affected product/version, vendor advisory, patch or mitigation, and exposure.
Exposure hint
authenticated boundary
Impact tags
Urgency reasons
Source-derived note
Summary derived from NVD / OSV description; unsafe procedural detail is not shown.
Redaction metadata
- source summary used
- True
- fallback summary used
- False
- unsafe procedural detail present
- false
- raw source displayed
- false
- public summary redacted
- true
Remediation handoff
Public-safe static handoff for human/Codex remediation planning. Scan, patch, external execution, and auto remediation are disabled.
Safety note
This radar shows source-published defensive context only. Exploit procedures, exploit strings, scanner commands, and auto-remediation are not provided.