Authentication bypass via unchecked biometric success callback
Published Jun 20, 2026 · Updated Oct 8, 2026
Authentication bypass in Capgo Capacitor Native Biometric before 12.128.2 allows attackers to evade Android biometric checks via hooking. AuthActivity.java's onAuthenticationSucceeded() calls finishActivity("success") without validating the result's CryptoObject, accepting a forged success callback. Exploitation requires access sufficient to instrument the Android application process; protected application access depends on how the consuming app uses the biometric result.
Summary
What happened
Authentication bypass in Capgo Capacitor Native Biometric before 12.128.2 allows attackers to evade Android biometric checks via hooking. AuthActivity.java's onAuthenticationSucceeded() calls finishActivity("success") without validating the result's CryptoObject, accepting a forged success callback. Exploitation requires access sufficient to instrument the Android application process; protected application access depends on how the consuming app uses the biometric result.
The record
- CVE
- CVE-2026-56294
- Published
- Jun 20, 2026
- Updated
- Oct 8, 2026
- Vendor
- Capgo
- Product
- Capacitor Native Biometric
- Classifications
- CWE-287, T1631
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 20, 2026CVE publishedPublication date reported by the CVE source.
- Oct 8, 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.
Activity data is delayed. The latest report is Sep 28, 2026.
Public exploit references
- Android biometric callback bypass Frida 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
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started