CVE-2026-56212

Capgo - Improper 2FA Enforcement Logic via Team Security Settings

LOW
3.8
CVSS Score
Published: June 20, 2026 at 12:14 AM UTC
Updated: October 7, 2026 at 01:45 PM UTC
1 product affected across 1 vendorCapgo

Using Capgo by Capgo?

Get instant alerts when new vulnerabilities affect Capgo - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
LOW3.8
Exploit prediction
EPSS 0.3%
SSVC
PoC

Description

Capgo before 12.128.2 contains an authentication logic flaw: a user with permission to manage team or organization security settings can enable mandatory two-factor authentication for all team members without first enabling 2FA on their own account. The application fails to verify the initiator's 2FA status before allowing the policy change, resulting in inconsistent security enforcement, potential administrative misuse, and lockout risk for team members.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 12.128.2
Vendor states this is fixed in 12.128.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

SSVC — Action Prioritization

SSVCPoCNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

3.8LOWVulnCheck
Attack Vector
NETWORK
Complexity
LOW
Privileges
HIGH
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
LOW
Integrity
LOW
Availability
NONE
Vector?

Quick Info

StatusDEFERRED
CWE
CWE-269

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card