# CVE-2026-124599: Hardcoded RSA Private Key and Public Key Exposure in GV-Face Android Application v2.2.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-q753-5564-242j

## What is CVE-2026-124599?

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

### Official description

The RSA cryptographic key material, including a private key and public key, is
embedded within the application package. Because Android applications can
be extracted and reverse engineered, storing private cryptographic keys
directly inside the client application may allow an attacker to recover the
keys and potentially use them to impersonate the application, decrypt protected
data, or generate unauthorized cryptographic operations.

Weakness: CWE-321 (Use of Hard-coded Cryptographic Key)

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


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

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

## Is CVE-2026-124599 being exploited?

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

## Fix prompt for AI coding agents

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

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

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

## Sources

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

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