CVE-2026-124598: An API key is hardcoded and retrievable from the GV-Face package
Source GCVE Database
Not known to be exploited · CVSS 7.5 High.
Data as of 10 Nov 2026, 04:20 UTC
Thin evidence
One scorer or none| CNA (GV) | CVSS 3.1 | 7.5 |
|---|
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 10 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 9 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| GV-Facetw.com.geovision.face | Affected
| Fixed in– |
AI-suggested
Since the vulnerability involves hardcoded credentials in the client app, remediation typically involves removing the key from the client and implementing secure key management practices such as using backend token exchange or secure vaults. Until an official fix is available, developers should avoid embedding sensitive keys in client applications.
Description
CVE-2026-124598 describes a vulnerability in the GV-Face package where an API key is hardcoded and can be extracted from the Android application. Because Android apps can be reverse engineered, embedding sensitive API credentials in the client app risks unauthorized access and misuse of the key. This vulnerability has a high severity with a CVSS score of 7.5, indicating a network attack vector with no privileges or user interaction required, and it impacts confidentiality.