Skip to main content
VulnerabilityPublished

CVE-2026-124602: The RSA cryptographic key material, including a private key and public key, is embedded within the

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-124602· Medium 6.2

Not known to be exploited · CVSS 6.2 Medium.

Data as of 10 Nov 2026, 04:32 UTC

CVSS 3.1 base score
6.2Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GV)CVSS 3.16.2
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
GV-Accesstw.com.geovision.gvaccesscontrolAffected
  • =1.6.1
Fixed in–

AI-suggested

Since the vulnerability arises from insecure key storage, the recommended mitigation is to avoid embedding private keys in client-side applications. Instead, keys should be securely stored in hardware-backed keystores or managed server-side. Monitor vendor advisories for any official fixes or updates.

Description

The GV-Access Android application embeds RSA cryptographic key material, including private and public keys, directly within its package. This practice exposes the keys to extraction and reverse engineering by attackers, potentially enabling impersonation of the application or unauthorized cryptographic operations.

References

Community reviews

Loading reviews…