CyberSecBulletin
CVE-2026-124598NVD status: Deferred

GV-Face: Use of Hard-coded Cryptographic Key

Published Updated By the CyberSecBulletin desk

CVE-2026-124598 is a high-severity use of hard-coded cryptographic key vulnerability in GV-Face from GeoVision, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected GV-Face versions: 2.2.1. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.23% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Check which version of GV-Face you run against the affected versions below, and install the vendor's latest release.
  2. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.

Affected products and versions

VendorProductAffected versionsFixed in
GeoVisionGV-Face2.2.1Not stated

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
NoneNo account or login is needed.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
NoneNothing can be modified.
Availability
NoneAvailability is not affected.

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N. Scored by CNA.

Official 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.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Use of Hard-coded Cryptographic Key

The product uses a hard-coded, unchangeable cryptographic key.

How developers prevent this class of flaw

  • Prevention schemes mirror that of hard-coded password storage.

More Use of Hard-coded Cryptographic Key vulnerabilities (CWE-321)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: partial).
  3. Record last changed materially (score, affected products, status or references).

References

Other vulnerabilities in GV-Face

All GV-Face vulnerabilities

Recent Use of Hard-coded Cryptographic Key vulnerabilities

Spotted an error? Tell us.