Account takeover via unrestricted credential validation
Published Jun 23, 2026 · Updated Jun 23, 2026
Credential validation in Capgo before 12.128.2 allows remote attackers to compromise accounts through password spraying or credential stuffing. The validate_password_compliance endpoint uses a privileged Supabase client to call signInWithPassword while accepting a public key, permitting any origin, and imposing no request throttling. Only the public Supabase key and a guessed or reused valid password are required; a successful check confirms credentials that permit account access.
Summary
What happened
Credential validation in Capgo before 12.128.2 allows remote attackers to compromise accounts through password spraying or credential stuffing. The validate_password_compliance endpoint uses a privileged Supabase client to call signInWithPassword while accepting a public key, permitting any origin, and imposing no request throttling. Only the public Supabase key and a guessed or reused valid password are required; a successful check confirms credentials that permit account access.
The record
- CVE
- CVE-2026-56234
- Published
- Jun 23, 2026
- Updated
- Jun 23, 2026
- Vendor
- Capgo
- Product
- Capgo
- Classifications
- CWE-307, CWE-942, T1110.004, T1110.003
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 23, 2026CVE publishedPublication date reported by the CVE source.
- Jun 23, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <12.128.2
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Capgo public-key credential-check proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo