API key is hardcoded and retrievable from the GV-Face package. Since
Android applications can be reverse engineered, embedding sensitive API
credentials directly in the client application may allow unauthorized users to
extract and misuse the key.
Analysis
Analysis and contextual insights are available on OpenCVE Cloud.
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| GeoVision Inc. | GV-Face | unaffected |
|
No data.
No data.
No data available yet.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
| Link | Providers |
|---|---|
| https://www.geovision.com.tw/cyber_security.php |
|
Tue, 10 Nov 2026 00:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | An API key is hardcoded and retrievable from the GV-Face package. Since Android applications can be reverse engineered, embedding sensitive API credentials directly in the client application may allow unauthorized users to extract and misuse the key. | |
| Title | Hardcoded API Key Discovered in GV-Face Android Application v2.2.1 | |
| First Time appeared |
Geovision Inc.
Geovision Inc. gv-face |
|
| Weaknesses | CWE-321 | |
| CPEs | cpe:2.3:a:geovision_inc.:gv-face:2.2.1:*:*:*:*:*:*:* cpe:2.3:a:geovision_inc.:gv-face:2.2.2:*:*:*:*:*:*:* |
|
| Vendors & Products |
Geovision Inc.
Geovision Inc. gv-face |
|
| References |
| |
| Metrics |
cvssV3_1
|
MITRE
Status: PUBLISHED
Assigner: GV
Published:
Updated: 2026-11-10T00:18:17.969Z
Reserved: 2026-11-09T01:42:46.616Z
Link: CVE-2026-124598
Vulnrichment
No data.
NVD
No data.
Redhat
No data.
OpenCVE Enrichment
No data.
-
CWE-321
Use of Hard-coded Cryptographic Key