GV-Eye Hardcoded API Key Vulnerability
Priority LOW 38CWE-312Published · Updated
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Information disclosure, Security bypass
- Confidentiality · integrity · availability
- High · None · None
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-312 and CWE-798.
Summary
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.
Why it matters now
Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00152 4th percentileScored 2026-11-07
Fix Fixed GV-Eye (GeoVision Inc.): V3.7.2
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- Yes
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
Remediation
- Fix · CNA GV-Eye (GeoVision Inc.) Fixed in V3.7.2
Timeline
- 2026-10-02 Threatist record created from CVE-2026-103096
- 2026-10-03 Alias added: GHSA-p7gq-p6v3-22xp
References
More GeoVision vulnerabilities
- TI-2024-10304 GeoVision EOL devices - OS Command Injection KEVCVSS 3.1CRITICAL 9.8
- TI-2024-05603 GeoVision EOL device - OS Command Injection KEVCVSS 3.1CRITICAL 9.8
- TI-2018-15344 GeoVision Command Injection RCE via /PictureCatch.cgi CVSS 4.0CRITICAL 10.0
- TI-2021-22411 GeoVision Geowebserver 5.3.3 - Local FIle Inclusion CVSS 4.0HIGH 8.7
- TI-2026-41681 GV-LPC2011/LPC2211 - unauthorized buffer overflow via RTSP Digest username (ssvr) CVSS 3.1CRITICAL 9.8
- TI-2026-41680 GV-LPC2011/LPC2211 - unauthorized buffer overflow via AuthMode/AuthValue path (ssvr) CVSS 3.1CRITICAL 9.8
Sources
- CVE-2026-103096 · CVE Program
- CVE-2026-103096 · NVD
- FIRST EPSS
- GHSA-p7gq-p6v3-22xp · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences