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

> Attackers can extract hardcoded API keys from the GV-Eye Android application to access payment services and bypass security controls.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Oct 2026
- **Updated:** 2 Oct 2026
- **Also known as:** GHSA-mwfx-8rgq-rc8f

## What is CVE-2026-103097?

CVE-2026-103097 is a high-severity vulnerability in GeoVision Inc. GV-Eye, published on 2 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

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

Weakness: CWE-798 (Use of Hard-coded Credentials), CWE-540 (Inclusion of Sensitive Information in Source Code), CWE-312 (Cleartext Storage of Sensitive Information)

## Which versions are affected by CVE-2026-103097?


## How do I fix CVE-2026-103097?

No fix has been published for CVE-2026-103097 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-103097 being exploited?

There is no known exploitation of CVE-2026-103097 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-103097 and fix it if it is affected.

What it is: CVE-2026-103097 is a high-severity vulnerability in GeoVision Inc. GV-Eye, published on 2 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-103097 in the wild and no public exploit code.

Affected product: GeoVision Inc. GV-Eye. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-103097/ (Markdown: https://insights.sbomify.com/CVE-2026-103097/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-103097
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-103097
- OSV: https://osv.dev/vulnerability/CVE-2026-103097

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-103097/
Summaries are generated and may contain mistakes; the official description above is the record.