Skip to content

← Actionable
Medium, CVSS 5.2amended

cap-go/capacitor-native-biometric Authentication Bypass

CVE-2026-56294GHSA-vx5f-vmr6-32wf

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (@capgo/capacitor-native-biometric 8.3.6), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
5.2 · CVSS:4.0/AV:P/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N · score source
EPSS
  • CVE-2026-56294: 0.24% estimated exploitation activity in the next 30 days; percentile 14.50 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

There is a potential issue with the cap-go/capacitor-native-biometric library. --- Summary The cap-go/capacitor-native-biometric library was found to be subject to an authentication bypass as the current implementation of the onAuthenticationSucceeded() does not appear to handle a CryptoObject[^HackTricks1] [^SecuringBiometricAuthentication] as seen in the following code block starting from line 88 in AuthActivity.java: As the current implementation only checks whether onAuthenticationSucceeded() was called and does not handle a CryptoObject the biometric authentication can be bypassed by hooking the onAuthenticationSucceeded() function. PoC Video: https://github.com/user-attachments/assets/b7b5a2bc-21dc-4373-b371-84b002dae7a7 Environment: The following steps were taken to create and deploy a Capacitor application using the cap-go/capacitor-native-biometric library for the purpose of verifying this finding. Note at the time of writing the npx create-react-app command broke, so I have…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-vx5f-vmr6-32wf

  2. Revision 2 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 1 · created ·

    Published from osv record GHSA-vx5f-vmr6-32wf

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-56294

Advisory: cap-go/capacitor-native-biometric Authentication Bypass
IDs: CVE-2026-56294, GHSA-vx5f-vmr6-32wf
Record: https://patchnext.com/advisories/cve-2026-56294 (revision 3, source checked 26 Oct 2026, 12:42 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.2)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: @capgo/capacitor-native-biometric 8.3.6. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @capgo/capacitor-native-biometric: affected < 8.3.6; fixed in 8.3.6

## Suggested inspection (read-only)
- `npm ls @capgo/capacitor-native-biometric --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @capgo/capacitor-native-biometric.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-vx5f-vmr6-32wf (OSV record GHSA-vx5f-vmr6-32wf lists affected ranges: npm @capgo/capacitor-native-biometric >=0 <8.3.6 (fixed))
- Verified: https://github.com/advisories/GHSA-vx5f-vmr6-32wf (GitHub-reviewed advisory GHSA-vx5f-vmr6-32wf lists affected ranges: npm @capgo/capacitor-native-biometric >=0 <8.3.6)

Commands are suggestions: review each one before running it.

Loading voting…