Description
An API key is
hardcoded and retrievable from the application 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.
Published: 2026-10-02
Score: 7.5 High
EPSS: n/a
KEV: No
Impact: Unauthorized access to payment API via exposed credentials
Action: Apply Patch
AI Analysis

Impact

The vulnerability allows an attacker to retrieve a hardcoded API key embedded in the GV-Eye Android application. Because the key can be extracted from the application package, malicious actors could gain unauthorized access to the payment relay service, potentially initiating fraudulent transactions or compromising financial data.

Affected Systems

This flaw affects the GeoVision Inc. GV-Eye Android application, specifically versions 3.6.0 and 3.7.2.

Risk and Exploitability

The CVSS score of 7.5 indicates high severity, while the EPSS score is not provided and the vulnerability is not yet listed in the CISA KEV catalog. Attackers can exploit it by reverse‑engineering the APK, extracting the API key, and reusing it to call the payment API. The vulnerability relies on an easily accessible client‑side credential, making exploitation straightforward for anyone able to decompile the application.

Generated by OpenCVE AI on October 2, 2026 at 02:24 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the official software update provided by GeoVision that removes the hardcoded credential.
  • Replace the embedded API key with a server‑side credential model, retrieving the key securely at runtime through authenticated channels.
  • Enforce transport layer security for all API calls and implement authentication headers or tokens that rotate regularly to limit the impact of any compromised key.

Generated by OpenCVE AI on October 2, 2026 at 02:24 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Fri, 02 Oct 2026 01:00:00 +0000

Type Values Removed Values Added
Description An API key is hardcoded and retrievable from the application 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 GV-Eye Relay Payment API Key Vulnerability
First Time appeared Geovision Inc.
Geovision Inc. gv-eye
Weaknesses CWE-312
CWE-540
CWE-798
CPEs cpe:2.3:a:geovision_inc.:gv-eye:v3.6.0:*:android:*:*:*:*:*
cpe:2.3:a:geovision_inc.:gv-eye:v3.7.2:*:android:*:*:*:*:*
Vendors & Products Geovision Inc.
Geovision Inc. gv-eye
References
Metrics cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N'}


Subscriptions

Geovision Inc. Gv-eye
cve-icon MITRE

Status: PUBLISHED

Assigner: GV

Published:

Updated: 2026-10-02T00:14:46.555Z

Reserved: 2026-09-30T02:10:01.788Z

Link: CVE-2026-103097

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-10-02T01:16:43.070

Modified: 2026-10-02T01:16:43.070

Link: CVE-2026-103097

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-10-02T02:30:18Z

Weaknesses
  • CWE-312

    Cleartext Storage of Sensitive Information

  • CWE-540

    Inclusion of Sensitive Information in Source Code

  • CWE-798

    Use of Hard-coded Credentials