# CVE-2026-124603: Hardcoded API Key Discovered in GV-Cloud Android Application v1.5.1

Status: published. Published: 2026-11-10. Updated: 2026-11-10.

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

## Remediation

No remediation reported in collected sources

## Affected products and versions

- GeoVision Inc. / GV-Cloud (tw.com.geovision.nativityGvloud): 1.5.1 (affected); 1.5.2 (unaffected). Source: CNA: GV; platforms: Android

## Severity and prioritization

- CVSS 3.1: 6.2 (medium); CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N; source: CNA: GV

- CISA KEV: No listing in collected sources

- EPSS: Not available

- SSVC: Not available

- Weaknesses: CWE-798

## Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

## References

- https://www.geovision.com.tw/cyber_security.php (CNA: GV)

## Provenance

- CNA: GV: https://www.cve.org/CVERecord?id=CVE-2026-124603; retrieved 2026-11-10; source updated 2026-11-10

Revision: ada94297f1029f5b2f0ee5415885b0b738bffff618023dbb2740287d65f277a6

Canonical: https://y2.dev/cve/CVE-2026-124603

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.