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


- **Severity:** Medium 6.2 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 10 Nov 2026
- **Updated:** 12 Nov 2026
- **Also known as:** GHSA-hvqx-58x9-7225

## What is CVE-2026-124603?

CVE-2026-124603 is a medium-severity vulnerability in GeoVision Inc. GV-Cloud, published on 10 Nov 2026. 

### Official description

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.

Weakness: CWE-798 (Use of Hard-coded Credentials)

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


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

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

## Is CVE-2026-124603 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-124603 is a medium-severity vulnerability in GeoVision Inc. GV-Cloud, published on 10 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-124603 in the wild and no public exploit code.

Affected product: GeoVision Inc. GV-Cloud. 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-124603/ (Markdown: https://insights.sbomify.com/CVE-2026-124603/index.md)
```

## Sources

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

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