# Hardcoded RSA Private Key and Public Key Exposure in GV-Face Android Application v2.2.1

CVE record · `CVE-2026-124599`

- **Identifiers:** `CVE-2026-124599`
- **State:** Confirmed
- **Severity:** CVSS 6.2 Medium
- **Critical:** No
- **CNA:** GV
- **Weakness (CWE):** [CWE-321](https://cwe.mitre.org/data/definitions/321.html)
- **Tags:** [Hard-coded credentials](https://agentprime.io/advisories/tag/hard-coded-credentials.md)
- **Technologies:** [GeoVision Inc. GV-Face](https://agentprime.io/advisories/technology/geovision-inc-gv-face.md)
- **Published:** 10 Nov 2026
- **Updated:** 12 Nov 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: GV) at 10 Nov 2026, 00:21 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Affected products, as the CNA wrote them

- Vendor: GeoVision Inc.. Product: GV-Face.
  - affected: `2.2.1`
  - unaffected: `2.2.2`
  - Other versions: unaffected
  - Package name: `tw.com.geovision.face`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> GeoVision GV-Face Android application version 2.2.1 embeds an RSA private key and public key inside the app package. An attacker who extracts and reverse engineers the app could recover the private key and use it to impersonate the application, decrypt protected data, or perform unauthorized cryptographic operations. Upgrade to version 2.2.2, which is listed as unaffected.

Written 19 Nov 2026.

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

- 6.2 Medium, CVSS 3.1: `CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`, from CNA (GV)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0011, the 1st percentile, on 22 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 10 Nov 2026, 00:21 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2026-124599)
- 10 Nov 2026, 00:40 UTC: First seen by agentprime
- 10 Nov 2026, 01:17 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-124599)

## Sources

- [CVE List: CVE-2026-124599](https://www.cve.org/CVERecord?id=CVE-2026-124599)
- [NVD: CVE-2026-124599](https://nvd.nist.gov/vuln/detail/CVE-2026-124599)

### References from the CNA

- <https://dlcdn.geovision.com.tw/TechNotice/CyberSecurity/2026/Security_Advisory_GV-Eye-2026-09-01.pdf>

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2026-124599>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2026-124599/>. Everything for agents: <https://agentprime.io/llms.txt>.
