Hardcoded API Key Discovered in GV-Access Android Application v1.6.1

published 2026-11-10 2d ago modified 2026-11-10 2d ago also EUVD-2026-120670

cvss: 6.2; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.1%; EPSS 0.1% chance of exploitation in 30 days, percentile 1%
public exploits: 0; none known

An API key is hardcoded and retrievable from the GV-Access 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.

Patch / fix

fixed in 1

GeoVision Inc. GV-Access 1.6.2

Is CVE-2026-124601 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.11% chance of exploitation in the next 30 days, higher than 1% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by	version	score	vector
CNA	3.1	6.2	CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Affected products

GeoVision Inc. GV-Access

Classification

Weakness

CWE-798 Use of Hard-coded Credentials

References

geovision.com.tw /cyber_security.php

Sources

CVE List CVE-2026-124601
NVD CVE-2026-124601

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.